CN110972337B

CN110972337B - Data transmission method, device and system, SDAP entity and storage medium

Info

Publication number: CN110972337B
Application number: CN201811147848.1A
Authority: CN
Inventors: 王莹莹; 孙军帅; 黄学艳; 韩星宇; 易芝玲
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2018-09-29
Filing date: 2018-09-29
Publication date: 2021-09-14
Anticipated expiration: 2038-09-29
Also published as: CN110972337A

Abstract

The invention discloses a data transmission method, a device, a system, an SDAP entity and a storage medium, wherein the method comprises the following steps: when receiving a reestablishment instruction, an SDAP entity at a source sending end determines an SDAP PDU which is not sent in the current Qos Flow; and determining SDAP SDU corresponding to the SDAP PDU, and sending the SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the SDAP SDU according to the Qos Flow to which the SDAP SDU belongs and the mapping relation between the Qos Flow stored by the target sending end SDAP entity and the data resource bearing DRB. The invention can ensure that the result obtained by analysis is consistent with the analysis result to be obtained, and can ensure the accuracy of the determined Reflective Qos.

Description

Data transmission method, device and system, SDAP entity and storage medium

Technical Field

The present invention relates to the field of wireless technologies, and in particular, to a data transmission method, apparatus, system, SDAP entity, and storage medium.

Background

In the 5G NR system, an SDAP (Service Data Adaptation Protocol) layer is introduced, where the SDAP layer is used to transmit Data of a user plane, implement mapping from Qos flows (Qos flows) of uplink and downlink Data to DRBs, add Qos Flow identifiers (Qos Flow IDs) to uplink and downlink Data flows, and complete mapping of reflexive Qos.

As shown in fig. 1, for a sending end, the SDAP layer maps Data on the Qos Flow to a DRB (Data Resource Bearer) meeting a mapping relationship between the Qos Flow and the DRB according to the stored mapping relationship, where the DRB is specifically used for Data Bearer between the terminal and the base station, and if the DRB is configured with the SDAP header, adds the SDAP header to the Data, and then sends the Data to a PDCP (Packet Data Convergence Protocol) layer, and if the DRB is not configured with the SDAP header, directly sends the Data to the PDCP layer. The PDCP layer is transmitted to a receiving end through a Radio Interface (Uu) Radio Interface. For the receiving end, if the SDAP layer determines that the DRB where the received data is located configures the SDAP header, the SDAP layer performs the mapping processing from Reflective QoS Flow to the DRB, removes the SDAP header of the received data and then delivers the data to the upper layer, and if not, directly delivers the received data to the upper layer.

The SDAP layer maps the Qos Flow data to the corresponding DRB, and in the reestablishment, if a base station communicated with the UE is switched from a source base station to a target base station, the corresponding SDAP is also switched from the source SDAP to the target SDAP, two types of data exist in a source gNB (source base station), namely the source base station, one type of the data is the Qos Flow data received from the core network, and the other type of the data is the data on the DRB processed by the SDAP layer. At this time, if the data on the DRB processed by the SDAP layer is directly forwarded to the receiving end through the target base station, since the mapping relationships stored in the source base station and the receiving end may be different, the result of determining whether the SDAP header is configured on the DRB mapped to the DRB may be different after the receiving end receives the data, which may cause inconsistency of the result of data analysis, and may also cause an accurate problem when mapping the Reflective Qos Flow to the DRB is performed, thereby causing inaccuracy of the finally determined Reflective Qos.

Disclosure of Invention

The invention provides a data transmission method, a device, a system, an SDAP entity and a storage medium, which are used for solving the problems that in the prior art, the result of analysis of data on a DRB processed by an SDAP layer of a source base station is inconsistent and the determined Reflective Qos is inaccurate due to base station switching in the reestablishing process.

The invention provides a data transmission method, which comprises the following steps:

when a source sending end service data adaptation protocol SDAP entity receives a reestablishment instruction, determining a first SDAP PDU which is not sent in the current quality of service Flow Qos Flow, wherein the reestablishment instruction is used for indicating that the source sending end SDAP entity is switched to a target sending end SDAP entity;

and determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the QoS Flow to which the first SDAP SDU belongs and the mapping relation between the QoS Flow and the DRB stored by the target sending end SDAP entity.

Further, the sending the first SDAP SDU to the target sender SDAP entity includes:

and sending the first SDAP SDU to the target sending end SDAP entity according to the sequence when the first SDAP SDU is received.

Further, the determining the first SDAP PDU not being sent in the current Qos Flow includes:

and according to the service type of the current Qos Flow, if the current Qos Flow needs to be confirmed, determining the SDAP PDU which does not pass the confirmation in the current Qos Flow as the first SDAP PDU which is not sent.

Further, if it is determined that the current Qos Flow does not require acknowledgement, the method further includes:

determining each second SDAP PDU not transmitted in the current Qos Flow;

and sending each second SDAP PDU to a source sending end PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

Further, the method further comprises:

clearing mapping from UL Qos Flow to DRB;

for a reflexive QoS, setting a QFI domain as an initial value, clearing the mapping relation from DL QoS Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB;

and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

Further, determining the first SDAP PDU that has not been transmitted includes:

and aiming at each SDAP PDU, determining the SDAP PDU with the carried label as the first SDAP PDU which is not sent in an uncompleted way according to the label which is carried by the SDAP PDU and used for feeding back the state of the SDAP PDU.

Further, the label of the failed acknowledgement carried in the SDAP PDU is determined when the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity is not received after the third SDAP PDU that fails to be acknowledged in the Qos Flow that needs to be acknowledged is sent to the corresponding source sending end PDCP entity.

Further, if the acknowledgement message of the third SDAP PDU sent by the source sending end PDCP entity is received, the method further includes:

the label carried by the third SDAP PDU is modified to a label that passes the acknowledgement.

Further, after the third SDAP PDU which fails to be confirmed in the Qos Flow to be confirmed is sent to the corresponding source sending end PDCP entity, the method further includes:

caching a second SDAP SDU corresponding to the third SDAP PDU;

after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the method further comprises:

and clearing the second SDAP SDU corresponding to the third SDAP PDU in the buffer and each remaining third SDAP SDU, and sending the subsequent third SDAP PDU.

a target sending end service data adaptation protocol SDAP entity receives a first SDAP SDU and determines the QoS Flow to which the first SDAP SDU belongs, wherein the first SDAP SDU is sent after determining the first SDAP SDU corresponding to a first SDAP PDU which is not sent in the current QoS Flow when a reestablishment instruction is received by a source sending end SDAP entity;

adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU;

and sending the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target SDAP entity.

Further, the sending the fifth SDAP PDU to the target sending end PDCP entity corresponding to the target SDAP entity includes:

and sending a fourth SDAP PDU corresponding to the first SDAP SDU to a target sending end PDCP entity corresponding to the target SDAP entity according to the sequence when the first SDAP SDU is received.

The invention provides a data transmission system, which comprises a source sending end SDAP entity, a target sending end SDAP entity and a target sending end PDCP entity; wherein the content of the first and second substances,

the source sending end SDAP entity is used for determining a first SDAP PDU which is not sent in the current quality of service Flow Qos Flow when a reestablishment instruction is received, wherein the reestablishment instruction is used for instructing to switch from the source sending end SDAP entity to the target sending end SDAP entity; determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity;

the target sending end SDAP entity is used for receiving a first SDAP SDU and determining the Qos Flow to which the first SDAP SDU belongs; adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU; and sending the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target SDAP entity.

Further, the source sending end SDAP entity is specifically configured to send the first SDAP SDU to the target sending end SDAP entity according to the sequence when receiving the first SDAP SDU.

Further, the target sending end SDAP entity is specifically configured to send, according to the sequence when the first SDAP SDU is received, a fourth SDAP PDU corresponding to the first SDAP SDU to a target sending end PDCP entity corresponding to the target SDAP entity.

Further, the source sending end SDAP entity is further configured to determine, according to the service type of the current Qos Flow, an SDAP PDU that fails to be confirmed in the current Qos Flow as a first SDAP PDU that is not sent, if it is determined that the current Qos Flow needs to be confirmed.

Further, the source sending end SDAP entity is further configured to determine, if it is determined that the current Qos Flow does not need to be confirmed, each second SDAP PDU that is not sent in the current Qos Flow; and sending each second SDAP PDU to a source sending end PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

Further, the source sending end SDAP entity is further configured to clear a mapping relationship from UL Qos Flow to DRB; for a reflexive QoS, setting a QFI domain as an initial value, clearing the mapping relation from DL QoS Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

Further, the source sending end SDAP entity is specifically configured to determine, for each SDAP PDU, an SDAP PDU with a carried label that fails to pass the acknowledgement as a first SDAP PDU that is not sent, according to the label that is carried by the SDAP PDU and used for feeding back the status of the SDAP PDU.

Further, the data transmission system further comprises a source sending end PDCP entity;

and the label of the failed confirmation carried in the SDAP PDU is determined when the confirmation information of the third SDAP PDU sent by the source sending end PDCP entity is not received after the third SDAP PDU which is failed to be confirmed in the QoS Flow needing confirmation is sent to the corresponding source sending end PDCP entity.

Further, the source sending end SDAP entity is further configured to modify, if receiving the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity, the label carried by the third SDAP PDU to a label that passes the acknowledgement.

Further, the source sending end SDAP entity is further configured to send a third SDAP PDU that fails to be confirmed in the Qos Flow that needs to be confirmed to the corresponding source sending end PDCP entity, and then cache a second SDAP SDU corresponding to the third SDAP PDU; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

Further, the data transmission system further includes: a target receiving terminal SDAP entity;

and the target receiving end SDAP entity is used for submitting a fifth SDAP PDU which is not sent in the current Qos Flow to the upper layer equipment in the reestablishment process.

Further, the target receiving end SDAP entity is further configured to clear mapping from UL Qos Flow to DRB; for a Reflective QoS, clearing Reflective mapping information, setting a QFI domain as an initial value, clearing a mapping relation from a DL QoS Flow to a DRB, and clearing a mapping relation from a UL QoS Flow to a DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

The invention provides a data transmission device, which is applied to a source sending end SDAP entity, and comprises the following components:

a determining module, configured to determine, when a re-establishment instruction is received, a first SDAP PDU that is not completely sent in a current Qos Flow, where the re-establishment instruction is used to instruct to switch from a source sending end SDAP entity to a target sending end SDAP entity;

and the sending module is used for determining a first SDAP SDU corresponding to the first SDAP PDU and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the target sending end SDAP entity.

The invention provides an SDAP entity, which comprises a memory, a processor and a transceiver;

the processor is used for reading the program in the memory and executing the following processes: when the transceiver is controlled to receive a reestablishment instruction, determining a first SDAP PDU which is not sent in the current Qos Flow, wherein the reestablishment instruction is used for instructing to switch from a source sending end SDAP entity to a target sending end SDAP entity; and determining a first SDAP SDU corresponding to the first SDAP PDU, and controlling the transceiver to transmit the first SDAP SDU to the target transmitting end SDAP entity, so that the target transmitting end SDAP entity adds an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the target transmitting end SDAP entity.

Further, the processor is specifically configured to control the transceiver to send the first SDAP SDU to the target sending-end SDAP entity according to a sequence when the first SDAP SDU is received.

Further, the processor is specifically configured to determine, according to the service type of the current Qos Flow, an SDAP PDU that does not pass through acknowledgement in the current Qos Flow as a first SDAP PDU that is not completely sent if it is determined that the current Qos Flow needs to be acknowledged.

Further, the processor is further configured to determine each second SDAP PDU that is not sent in the current Qos Flow if it is determined that the current Qos Flow does not require acknowledgement; and controlling the transceiver to send each second SDAP PDU to a source sending end PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

Further, the process is also for flushing UL Qos Flow to DRB mappings; for a reflexive QoS, setting a QFI domain as an initial value, clearing the mapping relation from DL QoS Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

Further, the processor is specifically configured to determine, for each SDAP PDU, an SDAP PDU that is not acknowledged with a carried label as the first SDAP PDU that is not finished to be sent, according to the label that is carried by the SDAP PDU and used for feeding back the status of the SDAP PDU.

Further, the processor is further configured to modify a label carried by the third SDAP PDU into a label passing the acknowledgement if receiving the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity.

Further, the processor is further configured to send a third SDAP PDU that fails to be confirmed in the Qos Flow that needs to be confirmed to the corresponding source sending end PDCP entity, and then cache a second SDAP SDU corresponding to the third SDAP PDU; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

The invention provides an SDAP entity, comprising: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;

the memory has stored therein a computer program which, when executed by the processor, causes the processor to perform the steps of the method described above as applied to any one of the source sender SDAP entities.

The present invention provides a computer readable storage medium storing a computer program executable by an SDAP entity, the program, when run on the SDAP entity, causing the SDAP entity to perform the steps of the method as applied to any one of source sender SDAP entities.

The invention provides a data transmission device, which is applied to a target sending end SDAP entity, and comprises the following components:

a determining module, configured to receive a first SDAP SDU, and determine a Qos Flow to which the first SDAP SDU belongs, where the first SDAP SDU is sent after determining, by an SDAP entity at a source sending end, a first SDAP SDU corresponding to a first SDAP PDU that is not sent in a current Qos Flow when a re-establishment instruction is received;

a sending module, configured to add an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and a mapping relationship between the Qos Flow and the DRB stored by the sending module, so as to obtain a fourth SDAP PDU; and sending the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target SDAP entity.

the processor is used for reading the program in the memory and executing the following processes: controlling the transceiver to receive a first SDAP SDU, and determining the Qos Flow to which the first SDAP SDU belongs, wherein the first SDAP SDU is sent after determining a first SDAP SDU corresponding to a first SDAP PDU which is not sent in the current Qos Flow when a source sending end SDAP entity receives a reestablishment instruction; adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU; and controlling the transceiver to send the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target SDAP entity.

Further, the processor is specifically configured to control the transceiver to send, according to the sequence when receiving the first SDAP SDU, a fourth SDAP PDU corresponding to the first SDAP SDU to a target sending end PDCP entity corresponding to the target SDAP entity.

the memory has stored therein a computer program which, when executed by the processor, causes the processor to perform the steps of the method described above as applied to any one of the target sender SDAP entities.

The present invention provides a computer readable storage medium storing a computer program executable by an SDAP entity, the program, when run on the SDAP entity, causing the SDAP entity to perform the steps of the method as described above as applied to any one of the target sender-side SDAP entities.

The invention provides a data transmission method, a device, a system, an SDAP entity and a storage medium, wherein the method comprises the following steps: when receiving a reestablishment instruction, an SDAP entity of a source sending end determines a first SDAP PDU which is not sent in the current Qos Flow, wherein the reestablishment instruction is used for instructing to switch from the SDAP entity of the source sending end to the SDAP entity of a target sending end; and determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the QoS Flow to which the first SDAP SDU belongs and the mapping relation between the QoS Flow stored by the target sending end SDAP entity and the data resource bearer DRB. In the invention, in the process of reestablishment, the SDAP entity of the source sending end sends SDAP SDU corresponding to SDAP PDU which is not sent in the current Qos Flow to the SDAP entity of the target sending end switched to in the reestablishment process, the SDAP entity of the target sending end reprocesses the SDAP SDU, so that the condition that the refiective Qos Flow obtained by parsing is consistent with the parsing result obtained by parsing when the SDAP of the receiving end carries out data parsing after the reprocessed data packet is sent to the SDAP entity of the receiving end can be ensured, and the accuracy of the determined refiective Qos can be ensured.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a diagram illustrating an overall function diagram of an SDAP layer in the prior art;

fig. 2 is a schematic structural diagram of a data transmission system according to embodiment 1 of the present invention;

fig. 3 is a schematic structural diagram of a data transmission system according to embodiment 7 of the present invention;

fig. 4 is a schematic diagram of a data transmission process according to embodiment 7 of the present invention;

fig. 5 is a schematic structural diagram of a data transmission system according to embodiment 9 of the present invention;

fig. 6 is a schematic diagram of a data transmission process according to embodiment 10 of the present invention;

fig. 7 is a schematic diagram of a data transmission process according to embodiment 12 of the present invention;

fig. 8 is a schematic structural diagram of an SDAP entity according to embodiment 14 of the present invention;

fig. 9 is a schematic structural diagram of an SDAP entity according to embodiment 15 of the present invention;

fig. 10 is a schematic structural diagram of an SDAP entity according to embodiment 17 of the present invention;

fig. 11 is a schematic structural diagram of an SDAP entity according to embodiment 18 of the present invention;

fig. 12 is a schematic diagram of a data transmission apparatus according to an embodiment of the present invention;

fig. 13 is a schematic diagram of a data transmission apparatus according to an embodiment of the present invention.

Detailed Description

In order to ensure the accuracy of the parsing result and the determined Reflective Qos in the re-establishment process, embodiments of the present invention provide a data transmission method, apparatus, system, SDAP entity, and storage medium.

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example 1:

fig. 2 is a schematic structural diagram of a data transmission system according to an embodiment of the present invention, where the data transmission system includes a source sending end SDAP entity 201, a target sending end SDAP entity 202, and a target sending end PDCP entity 203; wherein the content of the first and second substances,

the source sending end SDAP entity 201 is configured to determine a first SDAP PDU that is not finished to be sent in a current Qos Flow when a re-establishment instruction is received, where the re-establishment instruction is used to instruct to switch from the source sending end SDAP entity to a target sending end SDAP entity; determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity 202;

the target sending end SDAP entity 202 is configured to receive a first SDAP SDU, and determine a Qos Flow to which the first SDAP SDU belongs; adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU; and sending the fourth SDAP PDU to a target sending end PDCP entity 203 corresponding to the target SDAP entity.

In order to ensure the accuracy of the analysis result and the determined Reflective Qos in the reestablishment process, an embodiment of the present invention provides a data transmission system, where the data transmission system includes a source sending end SDAP entity, a target sending end SDAP entity, and a target sending end PDCP entity.

In the reestablishment process, which SDAP entity is to be switched to which SDAP entity may be indicated, at this time, the higher-layer device may send a reestablishment indication to the SDAP entity, the SDAP entity that receives the reestablishment indication may be referred to as a source sending end SDAP entity before switching in the reestablishment process, and in addition, the reestablishment indication may also indicate a target sending end SDAP entity to which the SDAP entity is to be switched in the reestablishment process, that is, the reestablishment indication is used to indicate to switch from the source sending end SDAP entity to the target sending end SDAP entity, and the reestablishment indication may be an RRC instruction.

When the source sending end SDAP entity receives the reestablishment indication, determining a first SDAP PDU which is not sent in the current Qos Flow, wherein the first SDAP PDU is data on the DRB processed by the source sending end SDAP entity, namely data added with a corresponding SDAP header.

The process of determining, by the SDAP entity, the SDAP PDU that is not completely sent in the current Qos Flow belongs to the prior art, and details are not described in the embodiment of the present invention.

Due to the mapping relationship between the Qos Flow and the DRB stored in the SDAP entity of the target sending end to which the handover is made, the mapping relationship between the Qos Flow and the DRB stored in the source sender SDAP entity may be consistent and may not be consistent, namely the mapping relation between the QoS Flow and the DRB stored in the receiving end SDAP entity corresponding to the target sending end SDAP entity, the mapping relationship between the Qos Flow and the DRB stored in the source sender SDAP entity may be consistent and may not be consistent, if the first SDAP PDU that is not completely transmitted is directly transmitted to the receiving-end SDAP entity through the target transmitting-end SDAP entity, the problem that the parsing result is inaccurate and the determined Reflective Qos is inaccurate may occur when the SDAP entity at the receiving end parses, therefore, in order to ensure the accuracy of the parsing result and the determined Reflective Qos in the re-establishment process, the source sending end SDAP entity can send a first SDAP SDU corresponding to a first SDAP PDU which is not sent to a target sending end SDAP entity.

The source sending end SDAP entity may determine a first SDAP SDU corresponding to a first SDAP PDU, specifically, the first SDAP SDU corresponding to the first SDAP PDU is stored in the source sending end SDAP entity, the source sending end SDAP entity directly searches for the first SDAP SDU corresponding to the first SDAP PDU, or the source sending end SDAP entity parses the first SDAP PDU according to the first SDAP PDU and a mapping relationship between stored Qos Flow and DRB, so as to obtain the first SDAP SDU corresponding to the first SDAP PDU, and the like.

When the source sending end SDAP entity sends the first SDAP SDU to the target sending end SDAP entity, the first SDAP SDU may be sent in any order, and certainly, for continuous sending of data, the first SDAP SDU may be sent in a specific order.

The target sending end SDAP entity can receive a first SDAP SDU sent by the source sending end SDAP entity, and can determine Qos Flow to which the first SDAP SDU belongs.

The process of determining the Qos Flow to which the SDAP SDU belongs by the SDAP entity belongs to the prior art, and details are not described in the embodiment of the present invention.

The target sending end SDAP entity can add an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the target sending end SDAP entity, so that the mapping relation between the Qos Flow and the DRB stored in the sending end SDAP entity and the receiving end SDAP entity is consistent, and the receiving end SDAP entity can ensure that the analysis result and the determined Reflective Qos are accurate during analysis.

The process of adding the SDAP header to the SDAP SDU by the SDAP entity belongs to the prior art, and is not described in detail in the embodiment of the invention.

And the target sending end SDAP entity adds an SDAP header to the first SDAP SDU to obtain a fourth SDAP PDU, and sends the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target sending end SDAP entity so that the target sending end PDCP entity sends the fourth SDAP PDU to a corresponding receiving end SDAP entity.

In the reestablishment process of the embodiment of the invention, the SDAP entity of the source sending end sends the SDAP SDU corresponding to the SDAP PDU which is not sent in the current Qos Flow to the SDAP entity of the target sending end which is switched to in the reestablishment process, the SDAP entity of the target sending end processes the SDAP SDU again, so that after the data packet which is processed again is sent to the SDAP entity of the receiving end, the analyzed result of the Reflective Qos Flow is consistent with the analyzed result when the SDAP of the receiving end analyzes the data, and the accuracy of the determined Reflective Qos can be ensured.

Example 2:

on the basis of the foregoing embodiment, in the embodiment of the present invention, the source sending end SDAP entity is specifically configured to send the first SDAP SDU to the target sending end SDAP entity according to the sequence when the first SDAP SDU is received.

The target sending end SDAP entity is specifically configured to send, according to the sequence when the first SDAP SDU is received, a fourth SDAP PDU corresponding to the first SDAP SDU to a target sending end PDCP entity corresponding to the target SDAP entity.

In order to avoid the situation that the data transmission is discontinuous in the reconstruction process of the SDAP entity, the SDAP entity may transmit the data according to the sequence of receiving the data when transmitting the data.

When the source sending end SDAP entity sends the first SDAP SDU to the target sending end SDAP entity, the source sending end SDAP entity may send the first SDAP SDU to the target sending end SDAP entity in sequence according to the sequence when the first SDAP SDU is received.

When the target sending end sends the fourth SDAP PDU to the corresponding target sending end PDCP entity, the target sending end may send the fourth SDAP PDU corresponding to the first SDAP SDU to the target sending end PDCP entity in sequence according to the sequence when the first SDAP SDU is received.

In the embodiment of the invention, the data are sent according to the sequence when the data are received, so that the condition that the data are sent discontinuously in the reconstruction process of the SDAP entity can be avoided, and the accuracy of data transmission is improved.

Example 3:

on the basis of the foregoing embodiments, in the embodiments of the present invention, the source sending end SDAP entity is further configured to determine, according to a service type of a current Qos Flow, an SDAP PDU that does not pass through acknowledgement in the current Qos Flow as a first SDAP PDU that is not sent completely if it is determined that the current Qos Flow needs to be acknowledged.

In the actual data sending process, some data relate to service data, and the accuracy requirement on the data analysis result is higher, so that the SDAP SDU corresponding to the data can be reprocessed by adopting the target sending end SDAP entity.

For the current Qos Flow, the source sending end SDAP entity may identify a service type of the current Qos Flow, and when identifying the service type of the current Qos Flow, the source sending end SDAP entity may store service types corresponding to different Qos flows, or may store the service types corresponding to different Qos flows in the current Qos Flow, and the like.

After the source sending end SDAP entity identifies the service type of the current Qos Flow, it may determine whether the current Qos Flow needs to be confirmed according to the service type of the current Qos Flow. Specifically, the information of whether the service type of the Qos Flow is the service type related to the service data is stored in the source sending end SDAP entity, at this time, the service type related to the service data of the current Qos Flow may be determined as requiring confirmation, and other service types unrelated to the service data are determined as not requiring confirmation; the information of whether the service type of the Qos Flow needs to be confirmed may be directly stored in the source sending end SDAP entity, and at this time, whether the service type of the Qos Flow needs to be confirmed may be directly determined according to the current service type of the Qos Flow.

For the current Qos Flow needing to be confirmed, determining the SDAP PDU which does not pass the confirmation in the current Qos Flow as a first SDAP PDU which does not complete transmission, so as to send the first SDAP SDU corresponding to the first SDAP PDU to the target sending end SDAP entity, and enabling the target sending end SDAP entity to regenerate the SDAP PDU corresponding to the first SDAP SDU, that is, the fourth SDAP PDU, so as to ensure the accuracy of final analysis of important data.

That is, during sending, for the Qos Flow that needs to be confirmed, the SDAP SDU is forwarded to the target base station SDAP, that is, the target receiving end SDAP entity, starting from the SDAP SDU corresponding to the SDAP PDU corresponding to the first PDCP PDU that does not pass through the bottom layer confirmation.

In the embodiment of the invention, the SDAP PDU which does not pass the confirmation in the current Qos Flow needing the confirmation is determined as the first SDAP PDU which does not complete the transmission, so that the first SDAP SDU corresponding to the first SDAP PDU is transmitted to the target transmitting end SDAP entity, and the accuracy of the final analysis of the important service data is ensured.

Example 4:

on the basis of the foregoing embodiments, in the embodiments of the present invention, the source sending end SDAP entity is further configured to determine, if it is determined that the current Qos Flow does not need to be confirmed, each second SDAP PDU that is not sent in the current Qos Flow; and sending each second SDAP PDU to a source sending end PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

In the actual data sending process, some data do not relate to service data, and the accuracy requirement on the data analysis result is not high, so that the data can be sent to the receiving terminal device without reprocessing, and the processing resource of the target sending terminal SDAP entity is further saved.

When determining that the current Qos Flow does not need to be confirmed, the source sending end SDAP entity may determine each second SDAP PDU that is not sent in the current Qos Flow, and send each second SDAP PDU to the source sending end PDCP entity corresponding to the source sending end SDAP entity, or directly send the source sending end PDCP entity to the receiving end.

Specifically, in order to ensure the continuity of data transmission during the reestablishment process, the source sending end SDAP entity may send each second SDAP PDU to the corresponding source sending end PDCP entity according to the sequence when receiving each second SDAP PDU, that is, for a Qos Flow that does not need to be confirmed, for an SDAP PDU that has not been submitted to the lower layer, the SDAP PDU is submitted to the PDCP entity according to the sequence of receiving an SDAP SDU from the upper layer.

In the embodiment of the invention, each second SDAP PDU which is not sent in the current Qos Flow and does not need to be confirmed is sent to the SDAP entity of the source sending end, so that the processing resource of the SDAP entity of the target sending end is saved, and the continuity of data sending is ensured.

Example 5:

on the basis of the foregoing examples, in the embodiment of the present invention, the source sending end SDAP entity is further configured to clear a mapping relationship from UL Qos Flow to DRB; for a reflexive QoS, setting a QFI (QFI Flow ID, quality of service Flow identifier) domain as an initial value, clearing the mapping relation from DL QoS Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

In order to ensure that the mapping relationship from the QoS Flow stored in the source sending end SDAP entity to the DRB can be updated in time, in the embodiment of the present invention, the mapping relationship stored in the SDAP entity may be reconfigured after the data that is not sent in the current QoS Flow is sent.

In the reconfiguration process, the mapping relation stored locally can be cleared at first, and specifically, the mapping relation from the UL Qos Flow to the DRB is cleared; and for the Reflective Qos, clearing Reflective mapping information, setting the QFI domain as an initial value, clearing the mapping relation from DL Qos Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB.

After the locally stored mapping relationship is cleared, the mapping relationship between Qos Flow and DRB carried in the RRC signaling sent by the higher layer may be reconfigured and stored, and specifically, the mapping relationship between Qos Flow and DRB carried in the RRC signaling may correspond to the cleared mapping relationship, that is, the mapping relationship between UL Qos Flow and DRB is carried, for a reflexive Qos, for Reflective mapping information, the information carried in the QFI domain is set, the mapping relationship between DL Qos Flow and DRB, and the mapping relationship between UL Qos Flow and DRB are carried.

In the embodiment of the invention, after the data which is not sent in the current Qos Flow is sent, the mapping relation stored in the SDAP entity is reconfigured, so that the mapping relation of the SDAP entity in the reestablishment process can be ensured to be updated in time.

Example 6:

on the basis of the foregoing embodiments, in the embodiment of the present invention, the source sending end SDAP entity is specifically configured to determine, for each SDAP PDU, an SDAP PDU whose carried label is not acknowledged as the first SDAP PDU that is not finished to be sent, according to the label, carried by the SDAP PDU, for feeding back the status of the SDAP PDU.

Because the SDAP layer does not have SN numbers, when the data forwarding is reestablished, whether the data packet is successfully sent or not cannot be judged by the SN numbers of the SDAP layer, and whether the data packet is repeatedly sent or not cannot be judged. In order to avoid the situation that data transmission is discontinuous or repeated in the reestablishment of the SDAP, the state of the SDAP PDU can be maintained by adopting a label, so that the SDAP entity at the source transmitting end can identify whether the state of the SDAP PDU is not confirmed.

And the source sending end SDAP entity determines the SDAP PDU with the carried label as the first SDAP PDU which is not sent completely according to the label for feeding back the SDAP PDU state carried in the SDAP PDU aiming at each SDAP PDU in the current Qos Flow.

If the label for feeding back the status of the SDAP PDU is the first label, the SDAP PDU is identified as a failed acknowledgement, and if the label for feeding back the status of the SDAP PDU is the second label, the SDAP PDU is identified as a passed acknowledgement.

In the embodiment of the invention, whether the SDAP PDU fails to be confirmed or not can be determined by the label of the feedback SDAP PDU state carried in the SDAP PDU, thereby avoiding the condition of discontinuous or repeated data transmission in the reestablishment process.

Example 7:

on the basis of the foregoing embodiments, in the embodiments of the present invention, as shown in fig. 3, the data transmission system further includes a source sending end PDCP entity 304;

And the source sending end SDAP entity is further configured to modify a label carried by the third SDAP PDU into a label passing the acknowledgement if the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity is received.

When the state of the SDAP PDU is maintained, the PDCP entity is matched with the SDAP entity to remember the maintenance of data forwarding, the SDAP PDU and the PDCP PDU are corresponding, and the state of the SDAP PDU is maintained through a state report fed back by the PDCP entity.

Before a source sending end SDAP entity receives a reestablishment instruction, a label which is not confirmed and is carried in a third SDAP PDU and the third SDAP PDU are sent to a source sending end PDCP entity corresponding to the source sending end SDAP entity, if the confirmation information of the third SDAP PDU sent by the source sending end PDCP entity is not received, the label carried in the third SDAP PDU is determined to be the label which is not confirmed, and if the confirmation information of the third SDAP PDU sent by the source sending end PDCP entity is received, the label carried in the third SDAP PDU is modified into the label which is confirmed.

The first label may also be used to uniquely label the third SDAP PDU when the label used to identify the failed acknowledgment is the first label.

As shown in fig. 4, the source SDAP is a source sending end SDAP entity, the source PDCP entity is a source sending end PDCP entity, the target SDAP is a target sending end SDAP entity, and the target PDCP entity is a target sending end PDCP entity, including the following steps:

the source SDAP carries a first label for feeding back the status of the SDAP PDU when sending the SDAP PDU to the PDCP. The first label corresponds to the PDCP PDU one to one. At each SDAP entity, the first label serves as a unique identification for the PDCP-identified SDAP PDU. The source SDAP layer may buffer the SDAP SDU corresponding to the first label while transmitting the SDAP PDU.

The flow of the source PDCP sending SDAP PDU status confirmation to the source SDAP layer is increased. The source PDCP entity needs to notify the source SDAP entity of the first label corresponding to the PDCP PDU that has been acknowledged in the current PDCP entity. The first label corresponding to the SDAP PDU corresponding to the confirmed PDCP PDU is referred to as a second label.

After the source SDAP receives the second label, it may be that the SDAP SDUs prior to the second label are emptied in the buffer, assuming that the SDAP PDUs were correctly received.

And the source SDAP forwards the SDAP SDUs after the last second label to the target SDAP according to the sequence.

In each PDCP sending entity, i.e., the source sending end PDCP entity, during the period from sending the PDCP PDU corresponding to the SDAP PDU to receiving end PDCP PDU confirmation, the SDAP PDU may be uniquely identified by the first label.

The SDAP defaults to the correct reception of SDAP PDUs sent prior to the second label when flow is reestablished. In the data switching process, the source SDAP forwards the SDAP SDUs which are not correctly received to the target base station SDAP according to the sequence. At this time, the PDCP does not perform the data forwarding procedure, and the TX _ NEXT corresponding to the PDCP layer of the target base station is reset to the initial value after the re-establishment.

The invention can realize the maintenance of the SDAP PDU state through the status report fed back by the PDCP entity, thereby determining whether the SDAP PDU fails to be confirmed.

Example 8:

on the basis of the foregoing embodiments, in the embodiments of the present invention, the source sending end SDAP entity is further configured to send a third SDAP PDU that fails to be confirmed in the Qos Flow that needs to be confirmed to the corresponding source sending end PDCP entity, and then buffer a second SDAP SDU corresponding to the third SDAP PDU; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

After the source sending end SDAP entity sends the third SDAP PDU which fails to be confirmed in the Qos Flow needing to be confirmed to the corresponding source sending end PDCP entity, the second SDAP SDU corresponding to the third SDAP PDU is cached, and the condition that data transmission is discontinuous or repeated in the process of reestablishment is avoided.

Because the third SDAP PDU is sent sequentially when the third SDAP PDU is sent, and the second SDAP SDU corresponding to the sent third SDAP PDU is cached, after it is determined that the label carried by the current third SDAP PDU is modified to a label that passes the confirmation, it can be considered that all the SDAP PDUs before the third SDAP PDU have been correctly received, and in order to avoid the occupation of the storage resource of the SDAP entity, the second SDAP SDU corresponding to the third SDAP PDU and each of the remaining third SDAP SDUs in the cache are removed, that is, the third SDAP PDU that has been successfully received and the SDAP SDU corresponding to the SDAP PDU before the third SDAP PDU are removed.

Example 9:

on the basis of the foregoing embodiments, in an embodiment of the present invention, as shown in fig. 5, the data transmission system further includes: target receiving end SDAP entity 505;

The target receiving end SDAP entity is also used for clearing mapping from UL Qos Flow to DRB; for a reflexive QoS, setting a QFI domain as an initial value, clearing the mapping relation from DL QoS Flow to DRB, and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

The data transmission system provided by the embodiment of the invention further comprises a target receiving end SDAP entity, and the target receiving end SDAP entity submits the fifth SDAP PDU which is not sent to the upper layer equipment when the fifth SDAP PDU which is not sent is existed in the current Qos Flow in the process of reestablishment.

In order to ensure that the mapping relationship of the SDAP entity can be updated in time during the reestablishment process, the mapping relationship stored in the target receiving end SDAP entity may be cleared, and reconfigured and stored after the fifth SDAP PDU in the current Qos Flow is sent.

Example 10:

on the basis of the foregoing embodiments, fig. 6 is a schematic diagram of a data transmission process provided in an embodiment of the present invention, where the process includes the following steps:

s601: and when a reestablishment instruction is received, determining a first SDAP PDU which is not sent in the current Qos Flow, wherein the reestablishment instruction is used for indicating that the source sending end SDAP entity is switched to the target sending end SDAP entity.

The data transmission method provided by the embodiment of the invention is applied to the SDAP entity of the source sending end.

S602: and determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the QoS Flow to which the first SDAP SDU belongs and the mapping relation between the QoS Flow stored by the target sending end SDAP entity and the data resource bearer DRB.

Example 11:

on the basis of the foregoing embodiment, in the embodiment of the present invention, the sending the first SDAP SDU to the target sending end SDAP entity includes:

determining each second SDAP PDU not transmitted in the current Qos Flow;

and sending each second SDAP PDU to a source sending end packet data convergence protocol PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

Further, the method further comprises:

clearing mapping from UL Qos Flow to DRB;

for a reflexive Qos, setting a QFI (quality of service) domain as an initial value, clearing the mapping relation from DL Qos Flow to DRB (data driven bus) and clearing the mapping relation from UL QoS Flow to DRB;

Further, determining the first SDAP PDU that has not been transmitted includes:

caching a second SDAP SDU corresponding to the third SDAP PDU;

Example 12:

on the basis of the foregoing embodiments, fig. 7 is a schematic diagram of a data transmission process provided in an embodiment of the present invention, where the process includes the following steps:

s701: and receiving a first SDAP SDU, and determining the QoS Flow to which the first SDAP SDU belongs, wherein the first SDAP SDU is sent after determining the first SDAP SDU corresponding to the first SDAP PDU which is not sent in the current QoS Flow when the source sending end SDAP entity receives the reestablishment indication.

The data transmission method provided by the embodiment of the invention is applied to the SDAP entity of the target sending end.

S702: and adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU.

S703: and sending the fourth SDAP PDU to a target sending end PDCP entity corresponding to the target SDAP entity.

Example 13:

on the basis of the foregoing embodiment, in the embodiment of the present invention, the sending the fifth SDAP PDU to the target sending end PDCP entity corresponding to the target SDAP entity includes:

Example 14:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides an SDAP entity 800, as shown in fig. 8, including: a processor 801, a memory 802, and a transceiver 803;

the processor 801 is configured to execute the program in the read memory 802, and execute any one of the foregoing data transmission processes applied to the source sending end SDAP entity.

Based on the same inventive concept, the embodiment of the present invention further provides an SDAP entity, and since the principle of the SDAP entity for solving the problem is similar to the data transmission method, the implementation of the SDAP entity may refer to the implementation of the method, and repeated details are omitted.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 801 and various circuits of memory represented by memory 802 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The transceiver 803 may be a plurality of elements including a transmitter and a receiver providing a means for communicating with various other apparatus over a transmission medium. The processor 801 is responsible for managing the bus architecture and general processing, and the memory 802 may store data used by the processor 801 in performing operations.

Alternatively, the processor 801 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

In the embodiment of the invention, the SDAP SDU corresponding to the SDAP PDU which is not sent in the current Qos Flow is sent to the target sending end SDAP entity which is switched to in the reestablishing process, the target sending end SDAP entity processes the SDAP SDU again, so that the condition that the reflected Qos Flow obtained by analysis is consistent with the analysis result obtained by analysis when the receiving end SDAP carries out data analysis after the data packet which is processed again is sent to the receiving end SDAP entity can be ensured, and the accuracy of the determined reflected Qos can be ensured.

Example 15:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides an SDAP entity 900, as shown in fig. 9, including: the system comprises a processor 901, a communication interface 902, a memory 903 and a communication bus 904, wherein the processor 901, the communication interface 902 and the memory 903 are communicated with each other through the communication bus 904;

the memory 903 stores therein a computer program, which when executed by the processor 901, causes the processor 901 to perform any one of the above data transmission applied to the source sender SDAP entity.

The communication bus mentioned in the above-mentioned SDAP entity may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

The communication interface 902 is used for communication between the above-described SDAP entity and other devices.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Alternatively, the memory may be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a central processing unit, a Network Processor (NP), and the like; but may also be a Digital instruction processor (DSP), an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like.

In the embodiment of the present invention, when the processor executes the program stored in the memory, the SDAP SDU corresponding to the SDAP PDU that is not completely sent in the current Qos Flow is sent to the target sending end SDAP entity that is switched to in the reestablishing process, and the target sending end SDAP entity processes the SDAP SDU again, so that it can be ensured that after the data packet that is processed again is sent to the receiving end SDAP entity, the reflected Qos Flow obtained by parsing is consistent with the parsing result obtained by parsing when the receiving end SDAP performs data parsing, and the accuracy of the determined reflected Qos can be ensured.

Example 16:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides a computer storage readable storage medium, where a computer program executable by an SDAP entity is stored in the computer storage readable storage medium, and when the computer program runs on the SDAP entity, the computer storage readable storage medium enables the SDAP entity to perform any one of the foregoing data transmission applied to an source sending end SDAP entity when the computer program is executed by the SDAP entity.

The computer readable storage medium may be any available media or data storage device that can be accessed by the processor in the SDAP entity, including, but not limited to, magnetic storage such as floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc., optical storage such as CDs, DVDs, BDs, HVDs, etc., and semiconductor storage such as ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs), etc.

In the computer-readable storage medium provided in the embodiment of the present invention, a computer program is stored, and when the computer program is executed by a processor, the sending of an SDAP SDU corresponding to an SDAP PDU that is not sent in a current Qos Flow to a target sending end SDAP entity that is switched to in a reestablishing process is achieved, the target sending end SDAP entity processes the SDAP SDU again, so that it is ensured that, after a data packet that is processed again is sent to a receiving end SDAP entity, when the receiving end SDAP performs data analysis, a Reflective Qos Flow obtained by analysis is consistent with an analysis result that is obtained, and the accuracy of a determined Reflective Qos can be ensured.

Example 17:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides an SDAP entity 1000, as shown in fig. 10, including: a processor 1001, a memory 1002, and a transceiver 1003;

the processor 1001 is configured to execute the program in the read memory 1002, and execute any one of the above data transmission applied to the target sending end SDAP entity.

In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1001, and various circuits, represented by the memory 1002, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The transceiver 1003 may be a number of elements including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1002 may store data used by the processor 1001 in performing operations.

Alternatively, the processor 1001 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

Example 18:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides an SDAP entity 1100, as shown in fig. 11, including: the system comprises a processor 1101, a communication interface 1102, a memory 1103 and a communication bus 1104, wherein the processor 1101, the communication interface 1102 and the memory 1103 are communicated with each other through the communication bus 1104;

the memory 1103 has stored therein a computer program that, when executed by the processor 1101, causes the processor 1101 to perform any of the above-described data transmission applied to a target sender SDAP entity.

The communication interface 1102 is used for communication between the above-described SDAP entity and other devices.

Example 19:

on the basis of the foregoing embodiments, an embodiment of the present invention further provides a computer storage readable storage medium, where a computer program executable by an SDAP entity is stored in the computer storage readable storage medium, and when the computer program runs on the SDAP entity, the SDAP entity is enabled to implement any of the foregoing data transmission applied to a target sending end SDAP entity when executed.

Fig. 12 is a schematic diagram of a data transmission apparatus 1200 according to an embodiment of the present invention, which is applied to an source sending end SDAP entity, and includes:

a determining module 1201, configured to determine, when a reestablishment instruction is received, a first SDAP PDU that is not completely sent in a current quality of service Flow Qos Flow, where the reestablishment instruction is used to instruct to switch from a source sending end SDAP entity to a target sending end SDAP entity;

a sending module 1202, configured to determine a first SDAP SDU corresponding to the first SDAP PDU, and send the first SDAP SDU to the target sending-end SDAP entity, so that the target sending-end SDAP entity adds an SDAP header to the first SDAP SDU according to a Qos Flow to which the first SDAP PDU belongs, and a mapping relationship between the Qos Flow stored by the target sending-end SDAP entity and a data resource bearer DRB.

The sending module is specifically configured to send the first SDAP SDU to the target sending-end SDAP entity according to a sequence when the first SDAP SDU is received.

The determining module is specifically configured to determine, according to the service type of the current Qos Flow, the SDAP PDU that does not pass the confirmation in the current Qos Flow as the first SDAP PDU that is not sent, if it is determined that the current Qos Flow needs to be confirmed.

The sending module is further configured to determine each second SDAP PDU that is not sent in the current Qos Flow if it is determined that the current Qos Flow does not need to be acknowledged; and sending each second SDAP PDU to a source sending end packet data convergence protocol PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

The device further comprises:

a configuration module, configured to clear mapping of UL Qos Flow to DRB; for a reflexive Qos, setting a QFI (quality of service) domain as an initial value, clearing the mapping relation from DL Qos Flow to DRB (data driven bus) and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

The determining module is specifically configured to determine, for each SDAP PDU, an SDAP PDU with a carried label that fails to be confirmed as a first SDAP PDU that is not finished to be sent, according to the label carried by the SDAP PDU and used for feeding back the status of the SDAP PDU.

The determining module is further configured to modify a label carried by the third SDAP PDU into a label passing the acknowledgement if receiving the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity.

The determining module is further configured to cache a second SDAP SDU corresponding to a third SDAP PDU after the third SDAP PDU that fails to be confirmed in the Qos Flow that needs to be confirmed is sent to the corresponding source sending end PDCP entity; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

In the embodiment of the invention, the SDAP SDU corresponding to the SDAP PDU which is not sent in the current Qos Flow is sent to the target sending end SDAP entity which is switched to in the reestablishing process, the target sending end SDAP entity processes the SDAP SDU again, so that the condition that the refiective Qos Flow obtained by analysis is consistent with the analysis result obtained by analysis when the receiving end SDAP carries out data analysis after the data packet which is processed again is sent to the receiving end SDAP entity can be ensured, and the accuracy of the determined refiective Qos can be ensured.

Fig. 13 is a schematic diagram of a data transmission apparatus 1300 according to an embodiment of the present invention, which is applied to an SDAP entity at a target sending end, and includes:

a determining module 1301, configured to receive a first SDAP SDU, and determine a Qos Flow to which the first SDAP SDU belongs, where the first SDAP SDU is sent after determining, by an SDAP entity at a source sending end, a first SDAP SDU corresponding to a first SDAP PDU that is not sent in a current Qos Flow, when receiving a reestablishment instruction;

a sending module 1302, configured to add an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and a mapping relationship between the Qos Flow and the DRB stored by the sending module, so as to obtain a fourth SDAP PDU; and sending the fourth SDAP PDU to a target sending end packet data convergence protocol PDCP entity corresponding to the target SDAP entity.

The sending module is specifically configured to send, according to the sequence when the first SDAP SDU is received, the fourth SDAP PDU corresponding to the first SDAP SDU to the target sending-end PDCP entity corresponding to the target SDAP entity.

For the method/apparatus embodiment, since it is substantially similar to the system embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the system embodiment.

It is to be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or operation from another entity or operation without necessarily requiring or implying any actual such relationship or order between such entities or operations.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method of data transmission, the method comprising:

and determining a first SDAP SDU corresponding to the first SDAP PDU, and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the QoS Flow to which the first SDAP SDU belongs and the mapping relation between the QoS Flow stored by the target sending end SDAP entity and the data resource bearer DRB.

2. The method of claim 1, wherein the sending the first SDAP SDU to the target sender SDAP entity comprises:

3. The method of claim 1, wherein the determining a first SDAP PDU not completed for transmission in a current Qos Flow comprises:

4. The method of claim 3, wherein if it is determined that the current Qos Flow does not require acknowledgement, the method further comprises:

determining each second SDAP PDU not transmitted in the current Qos Flow;

5. The method of any one of claims 1-4, further comprising:

clearing mapping from UL Qos Flow to DRB;

6. The method of claim 3, wherein determining a first SDAP PDU that has not completed transmission comprises:

7. The method of claim 6, wherein the label of the failed acknowledgement carried in the SDAP PDU is determined when the acknowledgement information of the third SDAP PDU sent by the source sending end PDCP entity is not received after the third SDAP PDU which is failed to acknowledge in the QoS Flow needing acknowledgement is sent to the corresponding source sending end PDCP entity.

8. The method of claim 7, wherein if the acknowledgement information of the third SDAP PDU sent by the source transmitting side PDCP entity is received, the method further comprises:

9. The method according to claim 8, wherein after sending the third SDAP PDU that fails to be acknowledged in the Qos Flow that needs to be acknowledged to the corresponding source sending end PDCP entity, the method further comprises:

caching a second SDAP SDU corresponding to the third SDAP PDU;

10. A method of data transmission, the method comprising:

a target sending end service data adaptation protocol SDAP entity receives a first SDAP SDU and determines the quality of service Flow Qos Flow to which the first SDAP SDU belongs, wherein the first SDAP SDU is sent after determining the first SDAP SDU corresponding to the first SDAP PDU which is not sent in the current Qos Flow when a reestablishment instruction is received by a source sending end SDAP entity;

and sending the fourth SDAP PDU to a target sending end packet data convergence protocol PDCP entity corresponding to the target sending end SDAP entity.

11. The method of claim 10, wherein the sending the fourth SDAP PDU to a target sending PDCP entity corresponding to the target SDAP entity comprises:

12. A data transmission system is characterized in that the data transmission system comprises a source sending end service data adaptation protocol SDAP entity, a target sending end SDAP entity and a target sending end packet data convergence protocol PDCP entity; wherein the content of the first and second substances,

13. The system of claim 12, wherein the source-sender SDAP entity is specifically configured to send the first SDAP SDU to the target-sender SDAP entity in an order in which the first SDAP SDU is received.

14. The system of claim 12, wherein the target sending-end SDAP entity is specifically configured to send, according to the sequence when receiving the first SDAP SDU, the fourth SDAP PDU corresponding to the first SDAP SDU to the target sending-end PDCP entity corresponding to the target SDAP entity.

15. The system according to claim 12, wherein the source sending end SDAP entity is further configured to determine, according to a service type of a current Qos Flow, an SDAP PDU that does not pass acknowledgement in the current Qos Flow as a first SDAP PDU that is not completely sent, if it is determined that the current Qos Flow needs acknowledgement.

16. The system according to claim 15, wherein the source sending end SDAP entity is further configured to determine each second SDAP PDU that is not sent in the current Qos Flow if it is determined that the current Qos Flow does not require acknowledgement; and sending each second SDAP PDU to a source sending end PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

17. The system according to any of claims 12-16, wherein the source sender SDAP entity is further configured to clear a mapping relationship of UL Qos Flow to DRB; for a reflexive Qos, setting a QFI (quality of service) domain as an initial value, clearing the mapping relation from DL Qos Flow to DRB (data driven bus) and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

18. The system of claim 15, wherein the source sending end SDAP entity is specifically configured to, for each SDAP PDU, determine, according to a label carried in the SDAP PDU and used for feeding back a status of the SDAP PDU, an SDAP PDU with a label that is not acknowledged as a first SDAP PDU that is not finished to be sent.

19. The system of claim 18, wherein the data transmission system further comprises a source transmitting side PDCP entity;

20. The system of claim 19, wherein the source sending end SDAP entity is further configured to modify the label carried by the third SDAP PDU into a label passing the acknowledgement if receiving the acknowledgement message of the third SDAP PDU sent by the source sending end PDCP entity.

21. The system according to claim 20, wherein the source sending end SDAP entity is further configured to buffer a second SDAP SDU corresponding to a third SDAP PDU that is not acknowledged in the Qos Flow that needs to be acknowledged, after sending the third SDAP PDU to the corresponding source sending end PDCP entity; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

22. The system of claim 12, wherein the data transmission system further comprises: a target receiving terminal SDAP entity;

23. The system of claim 22, wherein the target receiver SDAP entity is further configured to flush UL QoS Flow to DRB mappings; for a Reflective QoS, clearing Reflective mapping information, setting a QFI (quality of service Flow identifier) domain as an initial value, clearing a mapping relation from a DL QoS Flow to a DRB (data base station), and clearing a mapping relation from a UL QoS Flow to the DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

24. A data transmission device is applied to a source sending end Service Data Adaptation Protocol (SDAP) entity, and comprises the following components:

and the sending module is used for determining a first SDAP SDU corresponding to the first SDAP PDU and sending the first SDAP SDU to the target sending end SDAP entity, so that the target sending end SDAP entity adds an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow stored by the target sending end SDAP entity and the data resource bearing DRB.

25. A service data adaptation protocol, SDAP, entity comprising a memory, a processor, and a transceiver;

the processor is used for reading the program in the memory and executing the following processes: when the transceiver is controlled to receive a reestablishment instruction, determining a first SDAP PDU which is not sent in the current quality of service Flow Qos Flow, wherein the reestablishment instruction is used for indicating that an SDAP entity at a source sending end is switched to an SDAP entity at a target sending end; and determining a first SDAP SDU corresponding to the first SDAP PDU, and controlling the transceiver to transmit the first SDAP SDU to the target transmitting end SDAP entity, so that the target transmitting end SDAP entity adds an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow stored by the target transmitting end SDAP entity and the data resource bearing DRB.

26. The SDAP entity of claim 25, wherein the processor is specifically configured to control the transceiver to send the first SDAP SDU to the target sender SDAP entity in an order in which the first SDAP SDU is received.

27. The SDAP entity of claim 25, wherein the processor is specifically configured to determine, according to a service type of a current Qos Flow, an SDAP PDU that does not pass acknowledgement in the current Qos Flow as a first SDAP PDU that is not completely sent, if it is determined that the current Qos Flow needs acknowledgement.

28. The SDAP entity of claim 27, wherein said processor is further configured to determine each second SDAP PDU not transmitted in said current Qos Flow if it is determined that acknowledgement is not required for said current Qos Flow; and controlling the transceiver to send each second SDAP PDU to a source sending end packet data convergence protocol PDCP entity corresponding to the source sending end SDAP entity according to the sequence when the SDAP SDU corresponding to each second SDAP PDU is received.

29. The SDAP entity of any of claims 25-28, wherein said processing is further for flushing UL Qos Flow to DRB mappings; for a reflexive Qos, setting a QFI (quality of service) domain as an initial value, clearing the mapping relation from DL Qos Flow to DRB (data driven bus) and clearing the mapping relation from UL QoS Flow to DRB; and carrying out configuration storage according to the mapping relation between the Qos Flow and the DRB carried in the received RRC signaling.

30. The SDAP entity of claim 27, wherein the processor is specifically configured to determine, for each SDAP PDU, an SDAP PDU that carries a label that fails to be acknowledged as a first SDAP PDU that is not completely transmitted, according to the label carried by the SDAP PDU and used for feeding back a status of the SDAP PDU.

31. The SDAP entity of claim 30, wherein the label of the unacknowledged flag carried in the SDAP PDU is determined when acknowledgement information of a third SDAP PDU that is not acknowledged in the Qos Flow that needs to be acknowledged is not received after the third SDAP PDU is sent to the corresponding source sending end PDCP entity.

32. The SDAP entity of claim 31, wherein the processor is further configured to modify the label carried by the third SDAP PDU into a label passing the acknowledgement if receiving the acknowledgement from the source transmitting PDCP entity.

33. The SDAP entity of claim 32, wherein the processor is further configured to buffer a second SDAP SDU corresponding to a third SDAP PDU that does not pass acknowledgement in the Qos Flow that needs to be acknowledged, after sending the third SDAP PDU to the corresponding source sending end PDCP entity; and after the label carried by the third SDAP PDU is modified into a label passing the confirmation, the second SDAP SDU corresponding to the third SDAP PDU in the cache and each remaining third SDAP SDU are removed, and the subsequent third SDAP PDU is sent.

34. A service data adaptation protocol, SDAP, entity, comprising: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;

the memory has stored therein a computer program which, when executed by the processor, causes the processor to carry out the steps of the method of any one of claims 1 to 9.

35. A computer readable storage medium storing a computer program executable by an SDAP entity to cause the SDAP entity to perform the steps of the method of any of claims 1 to 9 when the program is run on the SDAP entity.

36. A data transmission device is applied to a target sending end Service Data Adaptation Protocol (SDAP) entity, and the device comprises:

a determining module, configured to receive a first SDAP SDU, and determine a Qos Flow to which the first SDAP SDU belongs, where the first SDAP SDU is sent after determining, by an SDAP entity at a source sending end, a first SDAP SDU corresponding to a first SDAP PDU that is not sent in a current Qos Flow, when receiving a reestablishment indication;

a sending module, configured to add an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and a mapping relationship between the Qos Flow and the DRB stored by the sending module, so as to obtain a fourth SDAP PDU; and sending the fourth SDAP PDU to a target sending end packet data convergence protocol PDCP entity corresponding to the target SDAP entity.

37. A service data adaptation protocol, SDAP, entity comprising a memory, a processor, and a transceiver;

the processor is used for reading the program in the memory and executing the following processes: controlling the transceiver to receive a first SDAP SDU, and determining a quality of service Flow Qos Flow to which the first SDAP SDU belongs, wherein the first SDAP SDU is sent after determining a first SDAP SDU corresponding to a first SDAP PDU which is not sent in the current Qos Flow when a source sending end SDAP entity receives a reestablishment indication; adding an SDAP header to the first SDAP SDU according to the Qos Flow to which the first SDAP SDU belongs and the mapping relation between the Qos Flow and the DRB stored by the SDAP header, and obtaining a fourth SDAP PDU; and controlling the transceiver to send the fourth SDAP PDU to a target sending end packet data convergence protocol PDCP entity corresponding to the target SDAP entity.

38. The SDAP entity of claim 37, wherein the processor is specifically configured to control the transceiver to send, to the target sending-end PDCP entity corresponding to the target SDAP entity, a fourth SDAP PDU corresponding to the first SDAP SDU according to the sequence when the first SDAP SDU is received.

39. A service data adaptation protocol, SDAP, entity, comprising: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;

the memory has stored therein a computer program which, when executed by the processor, causes the processor to carry out the steps of the method of any one of claims 10 to 11.

40. A computer readable storage medium storing a computer program executable by an SDAP entity to cause the SDAP entity to perform the steps of the method of any of claims 10 to 11 when the program is run on the SDAP entity.