CN116233040A

CN116233040A - Data fragment reorganization method, device, equipment and storage medium

Info

Publication number: CN116233040A
Application number: CN202310157863.9A
Authority: CN
Inventors: 刘建德; 戴初举; 黎书生
Original assignee: Shenzhen Consys Technology Co ltd
Current assignee: Shenzhen Consys Technology Co ltd
Priority date: 2023-02-15
Filing date: 2023-02-15
Publication date: 2023-06-06

Abstract

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

Description

Data fragment reorganization method, device, equipment and storage medium

Technical Field

The present disclosure relates to communication technologies, and in particular, to a method, an apparatus, a device, and a storage medium for reorganizing data fragments.

Background

In order to ensure that the data can be successfully transmitted, the communication protocol provides that when the size of the complete data exceeds the available air interface time-frequency resource of the Medium Access Control (MAC) layer of the transmitting end equipment, the Radio Link Control (RLC) layer of the transmitting end equipment divides the complete data to form data fragments, the data fragments are encapsulated into Protocol Data Units (PDU) of the RLC layer, and the MAC layer of the transmitting end equipment transmits the PDU to the receiving end equipment.

In the prior art, each PDU received by the receiving end device may be stored in a scattered manner, and in order to obtain the complete data, the RLC layer of the receiving end device reorders each PDU and sequentially moves the PDUs to a continuous storage space to form a single block of complete data. The moving and splicing of the PDU in the storage space consumes a lot of time, which affects the efficiency of the receiving end device to obtain the complete data.

In summary, in the prior art, the efficiency of obtaining complete data by the receiving end device is low.

Disclosure of Invention

The application provides a data fragment reorganization method, a device, equipment and a storage medium, which are used for solving the problem of low efficiency of obtaining complete data by receiving end equipment in the prior art.

According to a first aspect of the present application, there is provided a data fragment reassembly method applied to a central processing unit CPU, where the CPU is located in a receiving end device, and the receiving end device further includes a secure processing chip, the method includes:

receiving at least one protocol data unit PDU sent by a radio link control protocol (RLC) layer of a sending end, wherein the PDU comprises an RLC protocol header and a data fragment formed by dividing an RLC layer service data unit (RLC SDU) by the RLC layer of the sending end;

Analyzing the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU;

storing the storage address information of homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU;

in response to the fact that homologous PDUs belonging to the same RLC SDU are received, sequentially sending storage address information of all the homologous PDUs to a safety processing chip according to the sequence of forming the RLC SDU, so that the safety processing chip sequentially reads data fragments in all the homologous PDUs according to the storage address information of all the homologous PDUs and forms the RLC SDU;

and receiving the RLC SDU sent by the security processing chip.

As an optional implementation manner, the slicing attribute information includes an RLC SDU identifier and a slicing sequence number;

storing the storage address information of the homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU, comprising:

acquiring storage address information of each PDU;

determining the PDU with the same identification of the belonging RLC SDU as a homologous PDU;

determining whether an address storage space exists in the corresponding RLC SDU of each homologous PDU;

if the existence is determined, storing the storage address information of the homologous PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU;

If the data is not stored, an address storage space of the corresponding RLC SDU of the homologous PDU is created, and the storage address information of the homologous PDU is stored in the address storage space of the corresponding RLC SDU according to the slicing sequence number of the homologous PDU.

As an optional implementation manner, the creating an address storage space of the corresponding RLC SDU includes:

and creating storage bits according to the preset number or the number of homologous PDUs, and determining the created storage bits as address storage spaces of corresponding RLC SDUs.

As an optional implementation manner, the storing the storage address information of the homologous PDU in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU includes:

for any one of the homologous PDUs, the following is performed:

if the storage bit corresponding to the fragment sequence number exists in the address storage space corresponding to the RLC SDU, storing the storage address information of the homologous PDU into the corresponding storage bit;

if the fact that the information storage bits corresponding to the slicing sequence numbers do not exist in the address storage space of the corresponding RLC SDU is determined, the storage bits are added in the address storage space of the corresponding RLC SDU according to the slicing sequence numbers of the homologous PDU, and the storage address information of the homologous PDU is stored in the storage bits corresponding to the slicing sequence numbers.

As an optional implementation manner, the storage address information includes a data fragment address; the method for sequentially sending the storage address information of each homologous PDU to the safety processing chip according to the order of forming the RLC SDUs comprises the following steps:

and sequentially reading the storage address information of each homologous PDU according to the sequence of each storage bit in the address storage space of the corresponding RLC SDU, and sending the data fragment address in each storage address information to the safety processing chip.

As an optional implementation manner, the slice attribute information further includes a slice type, where the slice type is any one of the following: a head piece, a tail piece and a middle piece;

after storing the storage address information of the homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU, the method further comprises the following steps:

reading last PDU address storage information stored in a last storage bit of a corresponding RLC SDU;

if the fragment type of the PDU corresponding to the last PDU address storage information is determined to be a tail fragment and the fragment sequence numbers of the homologous PDU in each storage bit of the corresponding RLC SDU are continuous, determining that each PDU of the corresponding RLC SDU is received.

As an alternative embodiment, the RLC SDU includes a side chain relay adaptation protocol SRAP header or a packet data convergence protocol PDCP header;

acquiring SRAP (sequence-dependent access point) heads or PDCP heads of all RLC SDUs;

analyzing SRAP (sequence-related access point) heads or PDCP heads of all the RLC SDUs to obtain target protocol entity identification information of all the RLC SDUs;

and transmitting each RLC SDU to the target protocol entity based on the target protocol entity identification information of each RLC SDU.

According to a second aspect of the present application, there is provided a data fragment reassembly method applied to a secure processing chip, where the secure processing chip is located in a receiving end device, and the receiving end device further includes a CPU, the method includes:

sequentially receiving storage address information of all homologous PDUs sent by a CPU according to the order of forming the RLC SDUs;

sequentially reading data fragments in each homologous PDU according to the storage address information of each homologous PDU and forming an RLC SDU;

the RLC SDU is sent to the CPU.

As an optional implementation manner, the storage address information includes a data fragment address; the RLC SDU is RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained after a transmitting end packet data convergence protocol PDCP layer adopts a preset key to carry out first security processing; the first security process includes at least one of: encryption and integrity protection;

The reading the data segments in the homologous PDUs according to the storage address information of the homologous PDUs and forming the RLC SDUs sequentially comprises the following steps:

if the RLC SDU is the RLC SDU ciphertext, sequentially reading data fragments in all homologous PDUs from the data fragment addresses of all homologous PDUs to form the RLC SDU ciphertext;

the RLC SDU ciphertext is sent to the CPU, or a preset secret key is adopted to carry out second security processing on the RLC SDU ciphertext, an RLC SDU plaintext is obtained, and the RLC SDU plaintext is sent to the CPU; the second security process includes at least one of: decrypting and verifying the integrity;

and if the RLC SDU is the RLC SDU plaintext, sequentially reading the data fragments in each homologous PDU from the data fragment address of each homologous PDU to form the RLC SDU plaintext, and transmitting the RLC SDU plaintext to the CPU.

According to a third aspect of the present application, there is provided a data fragment reassembly apparatus applied to a CPU, where the CPU is located in a receiving end device, and the receiving end device further includes a secure processing chip, the apparatus includes:

a first receiving module, configured to receive at least one protocol data unit PDU sent by an RLC layer of a radio link control protocol of a transmitting end, where the PDU includes an RLC protocol header and a data segment formed by dividing an RLC layer service data unit RLC SDU by the RLC layer of the transmitting end;

The analysis module is used for analyzing the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU;

the storage module is used for storing the storage address information of homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU;

a first sending module, configured to send, in sequence, storage address information of each homologous PDU to a security processing chip according to an order of forming RLC SDUs in response to all homologous PDUs belonging to the same RLC SDU being received, so that the security processing chip reads data fragments in each homologous PDU in sequence according to the storage address information of each homologous PDU and forms RLC SDUs;

and the second receiving module is used for receiving the RLC SDU sent by the security processing chip.

According to a fourth aspect of the present application, there is provided a data slicing and reassembling apparatus applied to a secure processing chip, where the secure processing chip is located in a receiving end device, and the receiving end device further includes a CPU, the apparatus includes:

a third receiving module, configured to sequentially receive, according to an order of forming RLC SDUs, storage address information of each homologous PDU sent by the CPU;

the reorganization module is used for sequentially reading the data fragments in each homologous PDU according to the storage address information of each homologous PDU and forming an RLC SDU;

And the sending module is used for sending the RLC SDU to the CPU.

According to a fifth aspect of the present application, there is provided a receiving-end apparatus, including: a CPU, a security processing chip and a memory; the CPU includes a first transceiver; the secure processing chip includes a second transceiver;

the CPU, the secure processing chip and the memory circuit are interconnected;

the memory is used for storing first computer execution instructions and second computer execution instructions;

the first transceiver and the second transceiver are both used for receiving and transmitting data;

the CPU executes the first computer-executable instructions to implement the method as described in the first aspect, and the secure processing chip executes the second computer-executable instructions to implement the method as described in the second aspect.

According to a sixth aspect of the present application there is provided a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method as described in the first or second aspect.

The data fragment reorganization method, device, equipment and storage medium are applied to a CPU, wherein the CPU is located in receiving end equipment, the receiving end equipment further comprises a safety processing chip, and the method comprises the following steps: receiving at least one protocol data unit PDU sent by a radio link control protocol (RLC) layer of a sending end, wherein the PDU comprises an RLC protocol header and a data fragment formed by dividing an RLC layer service data unit (RLC SDU) by the RLC layer of the sending end; analyzing the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU; storing the storage address information of homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU; in response to the fact that homologous PDUs belonging to the same RLC SDU are received, sequentially sending storage address information of all the homologous PDUs to a safety processing chip according to the sequence of forming the RLC SDU, so that the safety processing chip sequentially reads data fragments in all the homologous PDUs according to the storage address information of all the homologous PDUs and forms the RLC SDU; and receiving the RLC SDU sent by the security processing chip. Because the storage address information of each homologous PDU is stored in the address storage space of the corresponding RLC SDU, after the homologous PDUs belonging to the same SDU are received, the storage address information of each homologous PDU is sequentially sent to the safety processing chip, the safety processing chip rapidly reads the data fragments in each homologous PDU through the storage address information of each homologous PDU, and then the data fragments in each homologous PDU are spliced to form the RLC SDU.

Drawings

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

Fig. 1 is a network architecture diagram corresponding to an application scenario of a data fragment reassembly method according to an embodiment of the present application;

fig. 2 is a flow chart of a data fragment reassembly method according to an embodiment of the present application;

fig. 3 is a flow chart of a data fragment reassembly method according to a second embodiment of the present application;

fig. 4 is a flow chart of a data fragment reassembly method according to a third embodiment of the present application;

fig. 5 is a flow chart of a data fragment reassembly method according to a fourth embodiment of the present application;

fig. 6 is a flow chart of a data fragment reassembly method according to a fifth embodiment of the present application;

fig. 7 is a schematic structural diagram of a data slicing and reorganizing device according to a sixth embodiment of the present application;

fig. 8 is a schematic structural diagram of a data slicing and reorganizing device according to a seventh embodiment of the present application;

fig. 9 is a schematic structural diagram of a receiving-end device according to an eighth embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

The terms referred to in this application are explained first.

The third generation partnership project (3rd Generation Partnership Project,3GPP), which is a standardization organization, sets out globally applicable communication Specifications (Specifications) from the third generation mobile communication system. The standard specifications established by 3GPP are managed with Release as a Release.

Long term evolution (Long Term Evolution, LTE), which is a long term evolution of the universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS) technical standard established by the 3GPP organization, has the first Release protocol LTE Release 8.

The packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer is one of the radio access protocol architectures of LTE Release 8 and later for IP header compression and decompression, encryption and decryption of data, integrity protection of data, etc.

The radio link control (Radio Link Control, RLC) layer, which is one of the radio access protocol architectures of LTE Release 8 and later for providing radio bearers for PDCP.

The medium access control (Medium Access Control, MAC) layer, which is one of the radio access protocol architectures of LTE Release 8 and later for providing logical channels for the RLC layer.

In release 16 standard (3GPP NR Release 16) and later releases of 3GPP, a side-chain relay adaptation protocol (Sidelink Relay Adaptation Protocol, SRAP) layer is added to the radio access protocol architecture in order to support communication between user terminals.

Protocol data units (Protocol Data Unit, PDUs), which are unit information exchanged between peer entities of layers of a computer network, correspond to data processed by the layers to form a specific format.

Service data units (Service Data Unit, SDU), which are data sets of user services of a given layer, correspond to data not processed in a certain layer.

Fragmentation (segment) is an operation of dividing an SDU by a transmitting end in order to ensure that each SDU to be transmitted can be transmitted.

Reassembly (reassembly) is the operation of the receiving end to splice the PDUs after they are received in order to obtain the complete data of the SDU.

In the protocols of LTE and later, it is specified that segmentation and reassembly are implemented by the RLC layer. Security processing, such as ciphering and/or integrity computation, is implemented by the PDCP layer.

The prior art to which the present application relates is described in detail and analyzed below.

In the communication process of the transmitting end equipment and the receiving end equipment, if the air interface time-frequency resource required by the complete RLC layer service data unit RLC SDU which is wanted to be transmitted by the RLC layer of the transmitting end equipment exceeds the air interface time-frequency resource which can be selectively used by the MAC layer of the transmitting end equipment, the RLC layer of the transmitting end equipment divides the RLC SDU into a plurality of data fragments according to the designated size of the MAC layer of the transmitting end equipment, adds an RLC layer protocol header before each data fragment, independently packages the data fragments into a protocol data unit RLC PDU of the RLC layer, and transmits the protocol data unit RLC PDU to the MAC layer of the transmitting end equipment. The plurality of RLC PDUs are transmitted to the receiving side device by the MAC layer of the transmitting side device.

The MAC layer of the receiving end device receives the plurality of RLC PDUs transmitted by the transmitting end device and delivers the RLC PDUs to the RLC layer of the receiving end device. And the RLC layer of the receiving end equipment reorganizes a plurality of RLC PDUs belonging to the same RLC SDU and acquires the RLC SDU, wherein the RLC PDUs are submitted by the MAC layer of the receiving end equipment in a specified time window.

Since the order in which each RLC PDU arrives at the receiving end device is not necessarily a slicing order, and the receiving end device may store each RLC PDU slice in a storage space of the receiving end device in a scattered manner after receiving each RLC PDU slice.

Meanwhile, the RLC SDU of the transmitting-side RLC layer comes from the transmitting-side PDCP layer, and the transmitting-side PDCP layer may perform a first security process on the RLC SDU, where the first security process includes at least one of the following: encryption, integrity protection. Thus, the RLC SDU may be RLC SDU ciphertext or RLC SDU plaintext before segmentation into data segments.

If the RLC SDU is RLC SDU ciphertext, after receiving the RLC SDU, the receiving end RLC layer needs to perform second security processing on the RLC SDU ciphertext by the receiving end PDCP layer to obtain RLC SDU plaintext. The second security process includes at least one of: decryption and integrity verification.

It will be appreciated that only full and consecutive RLC SDUs can be second security processed, but not data fragments or RLC PDUs.

However, whether the receiving end device needs to perform the second security processing on the RLC SDU or not, the RLC layer of the receiving end device needs to reassemble the RLC PDU into the RLC SDU after receiving all RLC PDU fragments belonging to the same RLC SDU, so that the subsequent processing can be performed. The process of reorganization is characterized in that the RLC layer of the receiving end device sorts the RLC PDU fragments belonging to the same RLC SDU and scattered in different storage positions in disorder, and the data fragments in the RLC PDU belonging to the same RLC SDU are moved to a storage space with continuous physical addresses according to the fragments in sequence, and are spliced to form a complete RLC SDU.

Because the movement and splicing of the data segments in the RLC PDU are performed in the storage space, a great amount of time is consumed, the time for the receiving terminal device to acquire the complete RLC SDU data is delayed, and the efficiency for the receiving terminal device to acquire the complete RLC SDU data is affected. In addition, when the number of fragments is large or a large number of RLC PDUs belonging to different RLC SDUs exist, the operation of moving and splicing the data fragments in the RLC PDUs also affects the efficiency of the receiving terminal device to acquire the complete RLC SDU data, and further affects the performance of the receiving terminal device.

To sum up, the data slicing reassembly method in the prior art needs to consume a great deal of time, and affects the efficiency of the receiving terminal device to acquire the complete RLC SDU data.

Therefore, when the problem in the prior art is faced, through creative research, in order to improve the efficiency of obtaining complete RLC SDU data by the receiving end device, the method that the efficiency is low and the CPU that can affect the performance of the receiving end device moves and splices PDU fragments in the memory space cannot be used to obtain SDUs, so that the CPU can only record the storage address information of each homologous PDU belonging to the same SDU, and after all homologous PDUs belonging to the same RLC SDU have been received, sequentially send the storage address information of each homologous PDU to the security processing chip according to the order of forming RLC SDUs, and the security processing chip sequentially reads the data fragments in each homologous PDU according to the storage address information of each homologous PDU and forms RLC SDU, so that the consumption time of moving and splicing PDU in the memory space by the CPU can be avoided, the performance of the receiving end device is affected, and simultaneously, the splicing and the possible second security processing can be directly completed by the security processing chip, thereby improving the efficiency of obtaining complete data by the receiving end device.

Therefore, the inventor proposes the technical scheme of the application, which is applied to a CPU, wherein the CPU is positioned in a receiving end device, the receiving end device further comprises a safety processing chip, and the method is used for receiving at least one protocol data unit PDU sent by a transmitting end radio link control protocol (RLC) layer, wherein the PDU comprises an RLC protocol header and a data segment formed by dividing an RLC layer service data unit (RLC SDU) by the transmitting end 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 PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU; in response to the fact that homologous PDUs belonging to the same RLC SDU are received, sequentially sending storage address information of all the homologous PDUs to a safety processing chip according to the sequence of forming the RLC SDU, so that the safety processing chip sequentially reads data fragments in all the homologous PDUs according to the storage address information of all the homologous PDUs and forms the RLC SDU; and receiving the RLC SDU sent by the security processing chip. Because the storage address information of each homologous PDU is stored in the address storage space of the corresponding RLC SDU, after the homologous PDUs belonging to the same SDU are received, the storage address information of each homologous PDU is sequentially sent to the safety processing chip, the safety processing chip rapidly reads the data fragments in each homologous PDU through the storage address information of each homologous PDU, and then the data fragments in each homologous PDU are spliced to form the RLC SDU.

The data fragment reorganization method, device, equipment and storage medium provided by the application aim to solve the technical problems in the prior art. The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

The network architecture and application scenario of the data fragment reassembly method provided in the embodiments of the present application will be described below. When the following description refers to the accompanying drawings, the same data in different drawings represents the same or similar elements, unless otherwise indicated.

Fig. 1 is a network architecture diagram corresponding to an application scenario of a data fragment reassembly method according to an embodiment of the present application. As shown in fig. 1, a network architecture corresponding to an application scenario provided in an embodiment of the present application includes: a transmitting end device 11 and a receiving end device 12. The receiving-side device 12 includes a CPU13 and a secure processing chip 14, and the CPU13 and the secure processing chip 14 may be connected by a bus. The transmitting-end device 11 includes a transmitting-end RLC layer 112 and a transmitting-end MAC layer 113. The receiving end device includes a receiving end MAC layer and a receiving end PDCP layer.

When the RLC layer service data unit RLC SDU to be transmitted exceeds the air interface time-frequency resource which can be selectively used by the sender MAC layer 113, the sender RLC layer 112 segments the RLC SDU to form a plurality of data fragments, as shown in fig. 1, and the RLC SDU is segmented into data fragment 1, data fragment 2, … …, and data fragment n.

The transmitting RLC layer 112 encapsulates the multiple data fragments independently after dividing the RLC SDU into multiple data fragments, that is, adds a protocol header of the RLC layer to each data fragment to form multiple protocol data units PDU, and as shown in fig. 1, data fragment 2, … …, and data fragment n form PDU1, PDU2, … …, and PDUn after adding the RLC layer protocol header. Therefore, each PDU includes an RLC protocol header and a data segment formed by segmentation of the RLC SDU by the transmitting-side RLC layer.

The transmitting-end RLC layer 112 transmits the plurality of PDUs to the transmitting-end MAC layer 113, and the transmitting-end MAC layer 113 transmits the plurality of PDUs to the receiving-end MAC layer via the physical layer through the air-interface time-frequency resource that can be selectively used.

The CPU13 of the receiving end device 12 receives each PDU through the receiving end MAC layer, and each received PDU is stored in the storage space of the receiving end device 12. The CPU13 may parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU, and may store the storage address information of the homologous PDU 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. After all the homologous PDUs belonging to the same RLC SDU have been received, the CPU13 may sequentially send the storage address information of each homologous PDU to the security processing chip 14 according to the order of forming RLC SDUs, so that the security processing chip 14 sequentially reads the data fragments in each homologous PDU according to the storage address information of each homologous PDU and forms RLC SDUs.

The security processing chip 14 sequentially receives the storage address information of each homologous PDU sent by the receiving terminal device according to the order of forming the RLC SDUs; sequentially reading data fragments in each homologous PDU according to the storage address information of each homologous PDU and forming an RLC SDU; the RLC SDU is sent to the CPU13.

The data fragment recombination method provided by the application can be applied to a 4G communication system or a 5G communication system. The transmitting end device and the receiving end device may be, but are not limited to, a 4G base station (Evolutional Node B, abbreviated eNB or eNodeB), a 5G base station (gndeb), a 4G mobile terminal, a 5G mobile terminal, or the like. For example, the transmitting device and the receiving device may be base stations, smartphones, tablet computers, smartwatches, and the like, which are not limited herein.

Embodiments of the present application will be described below with reference to the accompanying drawings. The embodiments described in the examples below do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

Example 1

Fig. 2 is a flow chart of a data fragment reassembly method according to an embodiment of the present application. As shown in fig. 2, the execution body of the present application is a data slicing and reassembling device, where the data slicing and reassembling device is located in a CPU, and the CPU is located in a receiving end device. The receiving end device also comprises a security processing chip. The data fragment reassembly method provided in this embodiment includes steps 201 to 205.

In step 201, at least one protocol data unit PDU sent by the sending end radio link control protocol RLC layer is received, where the PDU includes an RLC protocol header and a data segment formed by dividing an RLC layer service data unit RLC SDU by the sending end RLC layer.

In this embodiment, RLC SDU refers to SDU of RLC layer. RLC SDUs on the transmitting side device are transferred from the transmitting side PDCP layer to the transmitting side RLC layer. The PDU refers to a PDU of the RLC layer. When the size of the RLC SDU exceeds the air interface time-frequency resource which can be selectively used by the MAC layer of the transmitting end, the transmitting end RLC layer divides the RLC SDU data into a plurality of data fragments, and adds an RLC layer protocol header on each data fragment to form PDU of a plurality of RLC layers. That is, each PDU includes an RLC protocol header and a data segment formed by segmentation of RLC SDU data by the transmitting-side RLC layer.

And then the sending end MAC layer sends the PDUs to the protocol layer corresponding to the receiving end equipment. Here, since the transmitting MAC layer may choose to use different air time-frequency resources when transmitting each PDU, the transmitted PDUs do not necessarily arrive at the receiving device in the sequence of fragments.

The CPU receives the PDU through the receiving end MAC layer and stores the received PDU in the memory of the receiving end device, so that the CPU can acquire the storage address information of each PDU.

And 202, analyzing the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU.

In this embodiment, since the RLC SDU may be RLC SDU plaintext or RLC SDU ciphertext, the RLC SDU ciphertext is obtained after performing the first security process by using a preset key by the PDCP layer of the transmitting end. The first security process includes at least one of: encryption, integrity protection. Thus, the CPU may not be able to directly parse the data fragments in the PDU. However, the RLC layer adds a protocol header to the data segment without ciphering, so that after the receiving device receives the PDU, the RLC protocol header information of the PDU can be directly read to obtain the fragment attribute information of each PDU.

The slice attribute information is used to determine RLC SDUs to which each PDU belongs, and the order of data slices in each PDU in the RLC SDUs. For example, the fragmentation attribute information may include an RLC SDU identity and a fragmentation sequence number to which the PDU belongs.

The burst sequence number is used to identify the order of the data fragments in the PDU in the RLC SDU. Illustratively, the complete data is partitioned into 3 data segments: the first data segment, the second data segment and the third data segment are spliced in sequence to obtain complete data before being segmented. The sequence number of the PDU formed after the RLC layer protocol header is added to the first data segment may be 1, the sequence number of the PDU formed after the RLC layer protocol header is added to the second data segment may be 2, and the sequence number of the PDU formed after the RLC layer protocol header is added to the third data segment may be 3.

The CPU can determine whether each PDU belongs to the same RLC SDU and the sequence of each PDU belonging to the same RLC SDU according to the fragment attribute information of each PDU.

And step 203, storing the storage address information of the homologous PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU.

In this embodiment, the PDUs belonging to the same SDU identifier in the fragment attribute information belong to the same RLC SDU. The data fragments in the homologous PDU are obtained after being segmented by the same RLC SDU.

The storage address information may be a location where the PDU is stored in the receiving end device, for example, the storage address information may be a head address and a data length, a tail address and a data length, etc. of the PDU. Each PDU can be read from the memory of the receiving end device by the storage address information of the PDU.

The address storage space is a space in the memory of the receiving-end device for storing the above-described storage address information. In this embodiment, the storage address information of the homologous PDUs belonging to the same RLC SDU may be sequentially written into the address storage space of the corresponding RLC SDU according to the order of the PDUs.

And 204, in response to the received homologous PDUs belonging to the same RLC SDU, sequentially sending the storage address information of the homologous PDUs to the safety processing chip according to the order of forming the RLC SDU, so that the safety processing chip sequentially reads the data fragments in the homologous PDUs according to the storage address information of the homologous PDUs and forms an RLC SDU plaintext.

In this embodiment, the CPU may determine whether homologous PDUs belonging to the same RLC SDU have been received according to the parsing result of the RLC protocol header of each PDU. For example, the fragmentation attribute information may further include whether the data fragment in the PDU is the last data fragment after segmentation of the RLC SDU, and after the receiving device parses the PDU, it may be determined whether the PDU is the trailer of the RLC SDU according to the fragmentation attribute information of the PDU. If the PDU is determined to be the trailer in the corresponding RLC SDU, the CPU can determine whether the PDU included in the RLC SDU is all collected according to whether the sequence numbers of the fragments of the PDUs stored in the address storage space of the corresponding RLC SDU are continuous after storing the storage address information of the trailer PDU in the address storage space of the corresponding RLC SDU, and can determine whether the PDU of the corresponding RLC SDU is received according to the number of the received PDUs belonging to the RLC SDU when the trailer of the corresponding RLC SDU is read.

In this embodiment, the fragment attribute information of each PDU may be stored in the address storage space of the corresponding RLC SDU together with the stored address information.

In this embodiment, the storage address information of the PDU may include a data fragment address, where the data fragment address is a storage address of a data fragment in the PDU in the receiving end device. For example, the data fragment address may be a head address and a data length of the data fragment in a memory space of the receiving end device. The receiving end device sends the storage address information of each homologous PDU to the security processing chip in sequence. The security processing chip may perform RLC SDU formation from reading data fragments included in each of the homologous PDUs from each of the data fragment addresses in the order in which the storage address information of each of the homologous PDUs was received. That is, the RLC SDU is obtained by completing the concatenation of the data fragments by the security processing chip.

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

And step 205, receiving the RLC SDU plaintext sent by the security processing chip.

In this embodiment, the receiving end device stops after sending the storage address information of the trailer SDU to the security processing chip. The security processing chip reads data from the data fragment address of each homologous PDU in a bit stream mode, and outputs the formed RLC SDU plaintext in the bit stream mode, namely, sends the RLC SDU plaintext to the receiving end equipment. And the receiving terminal equipment receives the RLC SDU plaintext sent by the security processing chip.

The data fragment reassembly method provided by the embodiment is applied to a CPU, the CPU is located in receiving terminal equipment, the receiving terminal equipment further comprises a safety processing chip, and the method is used for receiving at least one protocol data unit PDU sent by a transmitting terminal radio link control protocol (RLC) layer, wherein the PDU comprises an RLC protocol header and a data fragment formed by dividing an RLC layer service data unit (RLC SDU) by the transmitting terminal 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 PDU belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU; in response to the fact that homologous PDUs belonging to the same RLC SDU are received, sequentially sending storage address information of all the homologous PDUs to a safety processing chip according to the sequence of forming the RLC SDU, so that the safety processing chip sequentially reads data fragments in all the homologous PDUs according to the storage address information of all the homologous PDUs and forms the RLC SDU; and receiving the RLC SDU sent by the security processing chip. Because the storage address information of each homologous PDU is stored in the address storage space of the corresponding RLC SDU, after the homologous PDUs belonging to the same SDU are received, the storage address information of each homologous PDU is sequentially sent to the safety processing chip, the safety processing chip rapidly reads the data fragments in each homologous PDU through the storage address information of each homologous PDU, and then the data fragments in each homologous PDU are spliced to form the RLC SDU.

Example two

Fig. 3 is a flow chart of a data fragment reassembly method according to a second embodiment of the present application. As shown in fig. 3, in the data fragment reassembly method provided in this embodiment, on the basis of the first embodiment, fragment attribute information includes an RLC SDU identifier and a fragment sequence number, and step 203 is refined, and step 203 refinement includes steps 301 to 305.

Step 301, obtaining storage address information of each PDU.

In this embodiment, after receiving the PDU, the receiving end device may store the PDU in its memory space, and obtain the storage address information of the PDU. The storage address information may include information of a head address, a tail address, a data length, etc. of the PDU as long as the PDU can be found in the memory of the receiving end device according to the storage information. Here, the head address, the tail address, etc. can be understood as the number of a storage unit in the memory. Since the PDU is formed after segmentation when the data amount of the RLC SDU is excessively large, the data amount of one PDU is limited, and the receiving end device stores the PDU in a storage unit with consecutive addresses when storing the PDU.

In step 302, the PDUs with the same RLC SDU identity are determined as the homologous PDUs.

In this embodiment, the RLC SDU identifier is added by the transmitting end when the data segments formed by dividing the SDU are encapsulated, that is, the RLC layer protocol header field added by the transmitting end includes the RLC layer identifier, and the plurality of data segments formed by dividing the same SDU have the same SDU identifier, so the receiving end device can determine the PDU with the same SDU identifier as the source PDU after parsing the fragment attribute information of the PDU. Here, more than one protocol header may be included in the protocol header field, for example, RLC layer protocol header and PDCP layer protocol header are included in the PDU of the RLC layer received by the receiving end.

In step 303, it is determined whether there is an address storage space for the corresponding RLC SDU of each homologous PDU.

In this embodiment, the receiving end device may receive one PDU at a time, or may receive multiple PDUs at a time, and the multiple PDUs received by the receiving end device at a time may be homologous PDUs belonging to the same RLC SDU, or may be non-homologous PDUs belonging to different RLC SDUs.

The corresponding RLC SDU of the PDU refers to the RLC SDU to which the PDU belongs. Since the RLC SDUs to which the homologous PDUs belong are identical, the corresponding RLC SDUs of the homologous PDUs are also identical.

In this embodiment, the CPU may allocate an address storage space for the RLC SDU when any one PDU of the RLC SDU is received, for storing storage address information of each PDU of the RLC SDU. Therefore, after the receiving end device acquires the fragment attribute information of each PDU, it is required whether the corresponding RLC SDU of each homologous PDU stores an address storage space.

In this embodiment, the CPU device may determine whether a PDU segment corresponding to the RLC SDU has been received within a specified time window, that is, whether a PDU segment belonging to the same RLC SDU as the PDU segment received this time has been received within a preset time period before the PDU segment received this time. If the PDU fragments of the corresponding RLC SDUs are determined to have been received, determining that the address storage space exists for the corresponding RLC SDUs of the homologous PDU, otherwise, if the PDU fragments of the corresponding RLC SDUs are determined to have not been received, determining that the address storage space does not exist for the corresponding RLC SDUs of the homologous PDU.

And step 304, if the existence is determined, storing the storage address information of the homologous PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU.

In this embodiment, if it is determined that the address storage space exists in the corresponding RLC SDU of the homologous PDU, the sequence of the homologous PDU may be determined according to the sequence number of the segmentation of the homologous PDU, so as to store the storage address information of the homologous PDU in the address storage space of the corresponding RLC SDU in sequence.

And step 305, if the data is determined not to exist, creating an address storage space of the corresponding RLC SDU of the homologous PDU, and storing the storage address information of each homologous PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU.

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

The data fragment reassembly method provided by the embodiment includes the belonging RLC SDU identifier and fragment sequence number in the fragment attribute information; acquiring storage address information of each PDU; determining the PDU with the same identification of the belonging RLC SDU as a homologous PDU; determining whether an address storage space exists in the corresponding RLC SDU of each homologous PDU; if the existence is determined, storing the storage address information of the homologous PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU; if the data is not stored, an address storage space of the corresponding RLC SDU of the homologous PDU is created, and the storage address information of the homologous PDU is stored in the address storage space of the corresponding RLC SDU according to the slicing sequence number of the homologous PDU. Since the storage address information is stored into the address storage space according to the fragment sequence number of the PDU when the address storage space exists in the corresponding RLC SDU, and the storage address information is stored into the address storage space after the address storage space is created when the address storage space does not exist in the corresponding RLC SDU, the storage address information of each PDU can be stored into the address storage space of the corresponding RLC SDU.

As an alternative implementation, based on the second embodiment, the refinement of "create address storage space of corresponding RLC SDU" in step 305, then the refinement includes step 401.

In step 401, a storage bit is created according to a preset number or the number of homologous PDUs, and the created storage bit is determined as an address storage space corresponding to the RLC SDU.

In this embodiment, the receiving end device cannot determine how many PDUs the RLC SDUs include in total before receiving the last PDU of the RLC SDUs, so the receiving end device 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 of the PDU formed after the RLC layer segments and repackages the RLC SDU. Illustratively, the RLC may split up to an RLC SDU into 100 data segments and repackage to form 100 PDUs. Accordingly, the preset number may be an upper limit of data segments formed by dividing the RLC SDU by the RLC layer, for example, the preset number may be 100.

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

In this embodiment, the number of homologous PDUs refers to the number of PDUs belonging to the same RLC SDU.

In this embodiment, the address storage space of the RLC SDU may also be a linked list structure, since the linked list stores information by nodes, that is, each node of the linked list is a storage bit. Each ring node of the linked list contains the address of the former ring node or the address of the latter ring node, so the linked list can be flexibly added or inserted into the nodes according to the requirement, and flexible serial connection between the nodes is realized. Therefore, when the address storage space of the RLC SDU is in a linked list structure, the receiving end device may create a node according to the number of homologous PDUs belonging to the same RLC SDU in each received PDU, and determine the created node as the storage space of the corresponding RLC SDU of the homologous PDU. And storing the storage address information of the homologous PDU into the node of the linked list.

For example, the receiving end device may create a linked list with the number of nodes being 2, and may determine 2 nodes of the created linked list as an address storage space of the first RLC SDU if the homologous PDU received and stored at one time by the receiving end device includes a first PDU with a fragment number of 1 and a third PDU with a fragment number of 3, where the first PDU and the third PDU belong to the first RLC SDU.

In summary, in this embodiment, the address storage space may be a linked list structure, an array structure, or the like, and the storage bits may be nodes of the linked list and elements of the array.

According to the data fragment reassembly method provided by the embodiment, the storage bits are created according to the preset number or the number of homologous PDUs, and the created storage bits are determined to be the address storage space of the corresponding RLC SDU. Since the storage bits are created by the preset number or the number of the homologous PDUs, it is possible to ensure that the storage address information of the currently stored homologous PDUs is stored into the address storage space of the corresponding PDUs.

As an optional implementation manner, on the basis of any one of the foregoing embodiments, the refinement of "store address information of each homologous PDU in address storage space of the corresponding RLC SDU according to the fragmentation sequence number of each homologous PDU" in step 304 and step 305 includes the following steps:

for any one of the homologous PDUs, the following is performed:

and if the storage bit corresponding to the fragment sequence number exists in the address storage space corresponding to the RLC SDU, storing the storage address information of the homologous PDU into the corresponding storage bit.

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 sequentially stored in each storage bit.

In this embodiment, if it is determined that the storage bit corresponding to the burst sequence number exists in the address storage space corresponding to the RLC SDU, when the address storage space corresponding to the RLC SDU is created, the storage bit storing the PDU storage address information of the burst sequence number is reserved, and the storage address information of the PDU is stored in the storage bit corresponding to the burst sequence number.

Illustratively, the homologous PDU received and stored by the CPU device this time includes a second PDU. The second PDU belongs to a first SDU, the address storage space of the first RLC SDU is an address storage array with the length of 100, and the slicing sequence number is 2. The CPU device stores the storage address information of the second PDU in the 2 nd element of the address storage array.

In this embodiment, if it is determined that the storage bit corresponding to the burst sequence number does not exist in the address storage space corresponding to the RLC SDU, the storage bit may be added to the address storage space according to the burst sequence number of each currently stored homologous PDU and the storage bit existing in the address storage space.

The homologous PDUs received and stored by the CPU at this time include a fifth PDU and a sixth PDU, where the fifth PDU and the sixth PDU belong to a first RLC SDU, an address storage space of the first RLC SDU is a linked list structure, and an address storage space of the RLC SDU is an address storage linked list. The slicing sequence number of the fifth PDU is 5, and the slicing sequence number of the sixth PDU is 6, the CPU may add 2 nodes in the address storage linked list to store the storage address information of the fifth PDU and the sixth PDU. And the sequence of each node in the linked list, the last node pointed to and the next node can be adjusted.

The data fragment reassembly method provided in this embodiment performs the following operations for any one homologous PDU: if the storage bit corresponding to the fragment sequence number exists in the address storage space corresponding to the RLC SDU, storing the storage address information of the homologous PDU into the corresponding storage bit; if the fact that the information storage bits corresponding to the slicing sequence numbers do not exist in the address storage space of the corresponding RLC SDU is determined, the storage bits are added in the address storage space of the corresponding RLC SDU according to the slicing sequence numbers of the homologous PDU, and the storage address information of the homologous PDU is stored in the storage bits corresponding to the slicing sequence numbers. When the storage bit corresponding to the slicing sequence number exists, the storage address information of the PDU is stored in the storage bit corresponding to the slicing sequence number, and when the storage bit corresponding to the slicing sequence number does not exist, the storage address information of the PDU is stored in the storage bit corresponding to the slicing sequence number after the storage bit is created, so that the storage address information of each PDU received at present can be ensured to be sequentially stored in the address storage space of the corresponding RLC SDU.

As an optional implementation manner, on the basis of any one of the foregoing embodiments, the storage address information includes a data fragment address, and the refinement of "the storage address information of each homologous PDU is sequentially sent to the security processing chip in order of forming the RLC SDU" in step 204 includes the following steps:

In this embodiment, the storage address information includes a data fragment address, where the data fragment address refers to a location of a data fragment in the PDU in the memory of the receiving end device. Here, in the communication protocol, the protocol header length of each layer may be fixed, and the protocol header field length in the data packet may be fixed, so that the data fragment address may be determined according to the storage address information of the PDU. Currently, the address of the data fragment may also be determined after parsing the header field of the PDU.

In this embodiment, since the PDU is obtained by adding the RLC layer protocol header after the RLC SDU is segmented, and the data segment in the RLC SDU is not obtained by the RLC layer protocol header, in order to obtain the complete data, the CPU may sequentially read the storage address information of each homologous PDU according to the order of the storage bits in the address storage space, and send the data segment address in each read storage address information to the security processing chip.

In this embodiment, the linked list is a data structure distributed in the storage space, and is used for recording the storage address information of the RLC SDU fragment data. The receiving end device can find the header address of the linked list, namely the first node address or other specific addresses in the linked list, through reading any node in the linked list, further can read all nodes of the whole linked list according to the sequence of the linked list, obtain the data fragment address of each PDU, and read each data fragment according to the sequence.

According to the data fragment reassembly method provided by the embodiment, the storage address information comprises the data fragment addresses, the storage address information of all the homologous PDUs is sequentially read according to the sequence of all storage bits in the address storage space of the corresponding RLC SDU, and the data fragment addresses in all the storage address information are sent to the safety processing chip. Because each data segment address is read in sequence according to the sequence of each storage bit in the address storage space of the corresponding RLC SDU and is sent to the safety processing chip, the CPU can rapidly read each data segment address and send encryption and decryption information, and the efficiency of acquiring the RLC SDU is improved.

Example III

Fig. 4 is a flow chart of a data fragment reassembly method according to a third embodiment of the present application. As shown in fig. 4, in the data slicing reassembly method provided in this embodiment, on the basis of any one of the foregoing embodiments, the slicing attribute information further includes a slicing type, where the slicing type is any one of the following: a head piece, a tail piece and a middle piece; further, after storing the storage address information of the homologous PDU belonging to the same RLC SDU in the address storage space of the corresponding RLC SDU according to the fragment attribute information of each PDU in step 203, steps 501 to 502 are further included.

In step 501, the last PDU address storage information stored in the last storage bit of the corresponding RLC SDU is read.

In this embodiment, since the storage address information of the PDU is stored in each storage bit in the address storage space in the sequence of fragments, the last PDU stored in the last storage bit must be the largest fragment sequence number in each PDU of the RLC SDU. Further, it may be determined whether a trailer PDU of an RLC SDU is received by determining whether the last PDU is a trailer of the RLC SDU.

In step 502, if it is determined that the fragmentation type of the PDU corresponding to the last PDU address storage information is the tail fragment and the fragmentation sequence numbers of the homologous PDUs in the storage bits of the corresponding RLC SDU are continuous, it is determined that each PDU of the corresponding RLC SDU has been received.

In this embodiment, the slice type may be obtained when the PDU is parsed in step 202, or may be obtained from the RLC protocol header of the PDU when the PDU is read. The slice type of the PDU is the first slice, the tail slice or the middle slice. Illustratively, the PDUs of the burst type first may include "SN" information in the RLC protocol header, and the PDUs of the burst type last may include "SI" information in the RLC protocol header. The "SN" information and the "SI" information are information used for identifying the first-slice PDU and the last-slice PDU in the RLC protocol header respectively.

It can be understood that the slice type of the PDU encapsulated by the first data segment after RLC SDU segmentation is the first slice, and the slice type of the PDU encapsulated by the last data segment is the last slice. Among the PDUs of one RLC SDU, only one of the PDUs of the slice type of the first slice or the last slice, and the PDUs of the slice type of the middle slice may be 0, 1 or more. And, since the first-slice PDU can be determined by the slice type, the protocol header in the first-slice PDU can not be added with the slice sequence number.

In this embodiment, if the fragment type of the PDU corresponding to the last PDU address storage information is a trailer, the address storage space in the storage bit is stored in the order of the PDUs after the PDUs are received and parsed. Therefore, the sequence numbers of the homologous PDUs in the storage bits corresponding to the RLC SDUs can be acquired sequentially from the first PDU, and in the process of reading the PDU with the first PDU as the segmentation type, the sequence numbers of the PDU are continuous, so that each PDU of the RLC SDUs can be determined to be received.

Of course, if the burst sequence number of the PDU is discontinuous during the process of reading the PDU of which the burst type is the first one, each PDU of the RLC SDU is not collected.

According to the data fragment reassembly method provided by the embodiment, the fragment attribute information further comprises a fragment type, and the fragment type is any one of the following: a head piece, a tail piece and a middle piece; reading last PDU address storage information stored in a last storage bit of a corresponding RLC SDU; if the fragment type of the PDU corresponding to the last PDU address storage information is determined to be the tail fragment and the fragment sequence numbers of the homologous PDU in each storage bit of the corresponding RLC SDU are continuous, determining that each PDU of the corresponding RLC SDU is received. The method comprises the steps of reading the fragmentation type of the last PDU through address storage information of the last PDU stored in the last storage bit of the corresponding RLC SDU, and sequentially reading the fragmentation sequence numbers of homologous PDUs in each storage bit of the corresponding RLC SDU when the fragmentation type of the last PDU is a tail fragment, and determining whether each PDU of the RLC SDU is collected or not under the condition that the fragmentation sequence numbers of the homologous PDUs are continuous in the process of reading the PDU with the fragmentation type being the first fragment.

Example IV

Fig. 5 is a flow chart of a data fragment reassembly method according to a fourth embodiment of the present application. As shown in fig. 5, the data fragment reassembly method provided in this embodiment includes a side chain relay adaptation protocol SRAP header or a packet data convergence protocol PDCP header in the RLC SDU based on any one of the above embodiments, and further includes steps 601 to 603 after receiving the RLC SDU sent by the security processing chip in step 205.

In step 601, an SRAP header or a PDCP header of each RLC SDU is obtained.

In this embodiment, the CPU may directly obtain the SRAP header or PDCP header from the RLC SDU plaintext. Meanwhile, since the PDCP layer is configured to perform the first security process or the second security process, for a data packet having encryption and/or integrity protection requirements, the PDCP layer at the transmitting end performs the first security process after adding the PDCP protocol header, to form an RLC SDU ciphertext, and transmits the RLC SDU ciphertext to the RLC layer at the transmitting end. For data packets without encryption and/or integrity protection requirements, the transmitting side PDCP layer forms RLC SDU plain text after adding a PDCP protocol header, and transmits to the transmitting side RLC layer. The SRAP header or PDCP header may also be obtained from the header field of the first slice PDU of the RLC SDU. Thus, the first-slice PDU may also include a protocol header of the packet data convergence protocol PDCP layer or a protocol header of the side-chain relay adaptation SRAP layer, as compared to the middle-slice PDU and the tail-slice PDU.

In this embodiment, the CPU may also obtain the SRAP header or PDCP header from the first PDU of the RLC SDU.

The security processing chip is hardware in the receiving end device, can logically belong to a hardware entity of the receiving end PDCP layer, is a part of the PDCP protocol entity, and is used for realizing the function of the receiving end PDCP protocol layer. For example, the RLC SDU ciphertext is subjected to a second security process.

The SRAP layer is located intermediate the PDCP layer and the RLC layer for forwarding data packets to other devices communicatively coupled to the receiving device.

Therefore, the receiving end device may obtain the SRAP header or PDCP header of the RLC SDU after receiving the RLC SDU plaintext or after receiving the first PDU, and parse the target protocol entity identification information of the RLC SDU.

Step 602, analyzing the SRAP header or PDCP header of each RLC SDU to obtain the target protocol entity identification information of each RLC SDU.

In this embodiment, the target protocol entity identification information includes a target receiving device and a target protocol entity, where the target receiving device may be a receiving end device, or may be another device communicatively connected to the receiving end device. The target protocol entity may be a protocol entity in the receiving end device, such as a PDCP protocol entity, or may be a protocol entity in another device communicatively coupled to the receiving end device, such as a PDCP protocol entity in another device communicatively coupled to the receiving end device.

And step 603, based on the target protocol entity identification information, transmitting the RLC SDU plaintext to the target protocol entity.

In this embodiment, the receiving end device may determine, according to the target receiving device and the target protocol entity, whether the RLC SDU plaintext needs to be sent to the PDCP layer or the SRAP layer of the receiving end device. The PDCP layer further processes the RLC SDU plaintext or the SRAP layer relays and forwards the RLC SDU plaintext.

In this embodiment, when relay forwarding is required to be performed on the RLC SDU plaintext, the SRAP layer sends the complete SDU to the RLC layer of the receiving end device, the RLC layer of the receiving end device segments and repackages the SDU again according to the air interface time-frequency resource of the MAC layer of the receiving end device to form a new RLC PDU, and the MAC layer of the receiving end device sends the new RLC PDU to the MAC layer of the target receiving device.

According to the data fragment reassembly method provided by the embodiment, the RLC SDUs comprise side chain relay adaptation protocol (SRAP) heads or Packet Data Convergence Protocol (PDCP) heads, and the SRAP heads or the PDCP heads of the RLC SDUs are obtained; analyzing SRAP (sequence-related access point) heads or PDCP heads of all the RLC SDUs to obtain target protocol entity identification information of all the RLC SDUs; and transmitting each RLC SDU to the target protocol entity based on the target protocol entity identification information of each RLC SDU. The SRAP header or the PDCP header is analyzed to acquire the identification information of the target protocol entity, so that the target receiving equipment of the RLC SDU can be determined, the RLC SDU is processed or forwarded to the target receiving equipment, and the processing efficiency of the receiving end equipment on the RLC SDU is improved.

Example five

Fig. 6 is a flow chart of a data fragment reassembly method according to a fifth embodiment of the present application. As shown in fig. 6, the data fragment reassembly method provided in this embodiment is applied to a secure processing chip, where the secure processing chip is located in a receiving device, and the receiving device further includes a CPU, and the method includes steps 701 to 702.

In step 701, storage address information of each source PDU sent by the CPU is sequentially received in order of forming RLC SDUs.

And step 702, reading the data fragments in each homologous PDU in sequence according to the storage address information of each homologous PDU and forming the RLC SDU.

In this embodiment, after receiving the storage address information of each homologous PDU, the security processing chip may determine the storage address of the data segment in each homologous PDU according to the storage address information of each homologous PDU, which is abbreviated as the data segment address, and may obtain the data segment in each homologous PDU from each data segment address by direct storage access DMA, and store the obtained data segment in a continuous space to form the RLC SDU.

In step 703, RLC SDUs are sent to the CPU.

In this embodiment, the security processing chip may send the storage address of the RLC SDU to the CPU, and the CPU may obtain the RLC SDU by accessing the storage address of the RLC SDU, or may directly send the formed RLC SDU to the CPU.

The data fragment reassembly method provided by the embodiment is applied to a safety processing chip, wherein the safety processing chip is positioned in receiving terminal equipment, and the receiving terminal equipment further comprises a CPU (Central processing Unit) for sequentially receiving storage address information of homologous PDUs sent by the CPU according to the sequence of forming RLC SDUs; sequentially reading data fragments in each homologous PDU according to the storage address information of each homologous PDU and forming an RLC SDU; the RLC SDU is sent to the CPU. The data fragments in the PDU are read from the storage space of the PDU through the safety processing chip, so that the overlarge power consumption of the CPU can be avoided, the performance of the receiving terminal equipment is influenced, and meanwhile, the speed of reading and writing data on the memory is very high because the safety processing chip is an application specific integrated circuit, the data fragments in the PDU can be spliced into RLC SDUs rapidly, and the efficiency of the receiving terminal equipment for acquiring the RLC SDUs is improved.

As an alternative embodiment, the storage address information includes a data fragment address; the RLC SDU is RLC SDU ciphertext or RLC SDU plaintext. The RLC SDU ciphertext is obtained after a transmitting end packet data convergence protocol PDCP layer adopts a preset key to carry out first security treatment; the first security process includes at least one of: encryption, integrity protection. According to the data fragment reassembly method provided in the present embodiment, based on the fifth embodiment, step 702 "sequentially reads the data fragments in each homologous PDU according to the storage address information of each homologous PDU and forms RLC SDU" is refined, and the refinement includes steps 7021 to 7023.

In step 7021, if the RLC SDU is RLC SDU ciphertext, the data segments in each homologous PDU are sequentially read from the data segment addresses of each homologous PDU to form RLC SDU ciphertext.

In this embodiment, since the RLC SDU is RLC SDU ciphertext, the data segments in the PDU are also ciphertext, and the security processing chip can splice the data segments in the homologous PDUs together through DMA to form RLC SDU ciphertext.

Step 7022, the RLC SDU ciphertext is sent to the CPU, or a preset key is adopted to perform a second security process on the RLC SDU ciphertext, so as to obtain RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security process includes at least one of: decryption and integrity verification.

In this embodiment, if the preset key is stored in the security processing chip, the RLC SDU ciphertext may be subjected to a second security process by using the preset key to obtain RLC SDU plaintext. The RLC SDU plaintext is stored in a continuous storage space of the receiving end device, and similarly, the security processing chip can send the storage address of the RLC SDU plaintext or the RLC SDU plaintext itself to the CPU.

If the security processing chip does not store the preset key, the RLC SDU ciphertext cannot be decrypted, and the storage address of the RLC SDU ciphertext can be directly sent to the CPU, or the RLC SDU ciphertext itself.

Step 7023, if the RLC SDU is RLC SDU plaintext, sequentially reading the data fragments in each homologous PDU from the data fragment address of each homologous PDU to form RLC SDU plaintext, and sending the RLC SDU plaintext to the CPU.

In this embodiment, if the RLC SDU is RLC SDU plaintext, the security processing chip may obtain RLC SDU plaintext after reading the data segment in each PDU, and send the memory address of the RLC SDU plaintext or the RLC SDU plaintext itself to the CPU.

The data fragment reorganization method provided by the embodiment includes that the storage address information includes data fragment addresses; the RLC SDU is RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained after a transmitting end packet data convergence protocol PDCP layer adopts a preset key to carry out first security treatment; the first security process includes at least one of: encryption and integrity protection; if the RLC SDU is the RLC SDU ciphertext, sequentially reading data fragments in all homologous PDUs from the data fragment addresses of all homologous PDUs to form the RLC SDU ciphertext; the RLC SDU ciphertext is sent to the CPU, or a preset secret key is adopted to carry out second security processing on the RLC SDU ciphertext, an RLC SDU plaintext is obtained, and the RLC SDU plaintext is sent to the CPU; the second security process includes at least one of: decrypting and verifying the integrity; if the RLC SDU is the RLC SDU plaintext, sequentially reading the data fragments in each homologous PDU from the data fragment address of each homologous PDU to form the RLC SDU plaintext, and sending the RLC SDU plaintext to the CPU. The safety processing chip can convert the RLC SDU ciphertext into the RLC SDU plaintext and send the RLC SDU plaintext, and can realize the safety processing function of the PDCP layer while splicing the PDU, so that the processing speed of the receiving terminal equipment on the RLC SDU can be improved.

Example six

Fig. 7 is a schematic structural diagram of a data slicing and reassembling apparatus according to a sixth embodiment of the present application. As shown in fig. 7, the data fragment reassembly apparatus 70 provided in this embodiment is applied to a CPU, where the CPU is located in a receiving end device, and the receiving end device further includes a security processing chip. The data fragment reassembly apparatus 70 includes:

the first receiving module 71 is configured to receive at least one protocol data unit PDU sent by the RLC layer of the transmitting end radio link control protocol, where the PDU includes an RLC protocol header and a data segment formed by dividing an RLC layer service data unit RLC SDU by the RLC layer of the transmitting end.

The parsing module 72 is configured to parse the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU.

And a storage module 73, configured to store, according to the fragment attribute information of each PDU, storage address information of homologous PDUs belonging to the same RLC SDU into an address storage space of a corresponding RLC SDU.

The first sending module 74 is configured to send, in response to the homologous PDUs belonging to the same RLC SDU being received, storage address information of each homologous PDU to the security processing chip in sequence according to an order of forming the RLC SDU, so that the security processing chip reads data fragments in each homologous PDU in sequence according to the storage address information of each homologous PDU and forms the RLC SDU.

And a second receiving module 75, configured to receive the RLC SDU sent by the security processing chip.

As an optional implementation manner, the slicing attribute information includes the RLC SDU identifier and the slicing sequence number; the storage module 73 is specifically configured to obtain storage address information of each PDU; determining the PDU with the same identification of the belonging RLC SDU as a homologous PDU; determining whether an address storage space exists in the corresponding RLC SDU of each homologous PDU; if the existence is determined, storing the storage address information of the homologous PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the homologous PDU; if the data is not stored, an address storage space of the corresponding RLC SDU of the homologous PDU is created, and the storage address information of the homologous PDU is stored in the address storage space of the corresponding RLC SDU according to the slicing sequence number of the homologous PDU.

As an alternative embodiment, the storage module 73 is specifically further configured to create storage bits according to a preset number or the number of homologous PDUs, and determine the created storage bits as an address storage space of the corresponding RLC SDU.

As an alternative embodiment, the storage module 73 is specifically further configured to, for any homologous PDU, perform the following operations: if the storage bit corresponding to the fragment sequence number exists in the address storage space corresponding to the RLC SDU, storing the storage address information of the homologous PDU into the corresponding storage bit; if the fact that the information storage bits corresponding to the slicing sequence numbers do not exist in the address storage space of the corresponding RLC SDU is determined, the storage bits are added in the address storage space of the corresponding RLC SDU according to the slicing sequence numbers of the homologous PDU, and the storage address information of the homologous PDU is stored in the storage bits corresponding to the slicing sequence numbers.

As an alternative embodiment, the first sending module 74 is specifically configured to sequentially read the storage address information of each homologous PDU according to the order of each storage bit in the address storage space of the corresponding RLC SDU, and send the data fragment address in each storage address information to the security processing chip.

As an optional implementation manner, the slice attribute information further includes a slice type, where the slice type is any one of the following: a head piece, a tail piece and a middle piece; the data fragment reassembly apparatus 70 further includes a determining module, configured to read last PDU address storage information stored in a last storage bit of a corresponding RLC SDU; if the fragment type of the PDU corresponding to the last PDU address storage information is determined to be the tail fragment and the fragment sequence numbers of the homologous PDU in each storage bit of the corresponding RLC SDU are continuous, determining that each PDU of the corresponding RLC SDU is received.

As an alternative embodiment, the RLC SDU includes a side chain relay adaptation protocol SRAP header or a packet data convergence protocol PDCP header; the first sending module is specifically further configured to obtain an SRAP header or a PDCP header of each RLC SDU; analyzing SRAP (sequence-related access point) heads or PDCP heads of all the RLC SDUs to obtain target protocol entity identification information of all the RLC SDUs; and transmitting each RLC SDU to the target protocol entity based on the target protocol entity identification information of each RLC SDU.

The data slicing and reassembling device provided in this embodiment may execute any one of the data slicing and reassembling methods provided in the first to fourth embodiments, and specific implementation manners are similar to the principle, and are not repeated here.

Example seven

Fig. 8 is a schematic structural diagram of a data slicing and reassembling apparatus according to a seventh embodiment of the present application. As shown in fig. 8, the data slicing reassembly apparatus 80 provided in this embodiment includes: a third receiving module 81, a reorganizing module 82 and a second transmitting module 83.

And a third receiving module 81, configured to sequentially receive, in order of forming RLC SDUs, storage address information of each homologous PDU sent by the CPU.

And the reassembly module 82 is configured to sequentially read the data segments in each homologous PDU according to the storage address information of each homologous PDU and form RLC SDUs.

And a second transmitting module 83, configured to transmit the RLC SDU to the CPU.

As an alternative embodiment, the storage address information includes a data fragment address; the RLC SDU is RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained after a transmitting end packet data convergence protocol PDCP layer adopts a preset key to carry out first security treatment; the first security process includes at least one of: encryption, integrity protection. The reassembly module 82 is specifically configured to sequentially read the data segments in each homologous PDU from the data segment addresses of each homologous PDU to form an RLC SDU ciphertext if the RLC SDU is an RLC SDU ciphertext; the RLC SDU ciphertext is sent to the CPU, or a preset secret key is adopted to carry out second security processing on the RLC SDU ciphertext, an RLC SDU plaintext is obtained, and the RLC SDU plaintext is sent to the CPU; the second security process includes at least one of: decrypting and verifying the integrity; if the RLC SDU is the RLC SDU plaintext, sequentially reading the data fragments in each homologous PDU from the data fragment address of each homologous PDU to form the RLC SDU plaintext, and sending the RLC SDU plaintext to the CPU.

The data slicing and reassembling device provided in this embodiment may execute any one of the data slicing and reassembling methods provided in the fifth embodiment, and specific implementation manners are similar to the principle, and are not repeated here.

Example eight

Fig. 9 is a schematic structural diagram of a receiving-end device according to a sixth embodiment of the present application. As shown in fig. 9, the receiving end device 90 provided in this embodiment includes: a CPU91, a secure processing chip 92, and a memory 93; CPU91 includes a first transceiver 910; the secure processing chip includes a second transceiver 920.

CPU91, secure processing chip 92, memory 93 circuit interconnect;

a memory 93 for storing first computer-executable instructions and second computer-executable instructions;

the first transceiver 910 and the second transceiver 920 are each configured to transmit and receive data;

the CPU91 executes the first computer execution instruction to implement any one of the data fragment reassembly methods provided in the first to fourth embodiments, and the security processing chip executes the second computer execution instruction to implement any one of the data fragment reassembly methods provided in the fifth embodiment, and the specific implementation manner is similar to the principle, and will not be repeated here.

The CPU91, the secure processing chip 92, and the memory 93 may be interconnected by a bus. The circuit interconnection can be realized through buses. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component Interconnect, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus.

The memory 93 may be implemented by any type of volatile or non-volatile memory device or 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 memory, flash memory, magnetic or optical disk, and the like.

In an exemplary embodiment, the receiver 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 elements for executing the methods described above.

The embodiments of the present application further provide a computer readable storage medium, where computer executable instructions are stored, where the computer executable instructions are used to implement the data fragment reassembly method provided in any one of the embodiments above when executed by a processor. By way of example, the computer-readable storage medium may be read-only memory (ROM), random-access memory (RAM), magnetic tape, floppy disk, optical data storage device, etc.

It should be understood that the above-described device embodiments are merely illustrative and that the device of the present application may be implemented in other ways. For example, the division of the modules in the above embodiment is merely a logic function division, and there may be another division manner when actually implemented. For example, multiple modules may be combined, or may be integrated into another system, or some features may be omitted or not performed.

In addition, each functional module in each embodiment of the present application may be integrated into one module, or each module may exist alone physically, or two or more modules may be integrated together, unless otherwise specified. The integrated modules may be implemented in hardware or in software program modules.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required in the present application.

It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. The data slicing and reorganizing method is characterized by being applied to a Central Processing Unit (CPU), wherein the CPU is located in receiving end equipment, the receiving end equipment further comprises a security processing chip, and the method comprises the following steps:

And receiving the RLC SDU sent by the security processing chip.

2. The method according to claim 1, wherein the segmentation attribute information includes an RLC SDU identifier and a segmentation sequence number;

acquiring storage address information of each PDU;

3. The method of claim 2, wherein creating an address storage space for the corresponding RLC SDU comprises:

4. The method of claim 3, wherein storing the storage address information of the homologous PDU in the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the homologous PDU comprises:

for any one of the homologous PDUs, the following is performed:

5. A method according to claim 3, wherein the storage address information includes a data fragment address; the method for sequentially sending the storage address information of each homologous PDU to the safety processing chip according to the order of forming the RLC SDUs comprises the following steps:

6. The method according to any one of claims 3-5, wherein the slice attribute information further includes a slice type, where the slice type is any one of the following: a head piece, a tail piece and a middle piece;

7. The method according to any of claims 1-5, wherein the RLC SDU comprises a side chain relay adaptation protocol, SRAP, header or a packet data convergence protocol, PDCP, header;

8. The data slicing and reorganizing method is characterized by being applied to a secure processing chip, wherein the secure processing chip is located in a receiving end device, the receiving end device further comprises a CPU, and the method comprises the following steps:

the RLC SDU is sent to the CPU.

9. The method of claim 8, wherein the storage address information includes a data fragment address; the RLC SDU is RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained after a transmitting end packet data convergence protocol PDCP layer adopts a preset key to carry out first security processing; the first security process includes at least one of: encryption and integrity protection;

10. A data slicing and reassembling apparatus, applied to a CPU, where the CPU is located in a receiving end device, and the receiving end device further includes a security processing chip, the apparatus includes:

11. A data slicing and reorganizing device, which is characterized by being applied to a secure processing chip, wherein the secure processing chip is located in a receiving end device, and the receiving end device further comprises a CPU, and the device comprises:

and the second sending module is used for sending the RLC SDU to the CPU.

12. A receiving-end apparatus, characterized by comprising: a CPU, a security processing chip and a memory; the CPU includes a first transceiver; the secure processing chip includes a second transceiver;

The CPU, the secure processing chip and the memory circuit are interconnected;

the CPU executes the first computer-executable instructions to implement the method of any one of claims 1-7, and the secure processing chip executes the second computer-executable instructions to implement the method of claim 8 or 9.

13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-9.