CN111417147B

CN111417147B - Data processing method, device, related equipment and storage medium

Info

Publication number: CN111417147B
Application number: CN201910013563.7A
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: 2019-01-07
Filing date: 2019-01-07
Publication date: 2023-05-05
Anticipated expiration: 2039-01-07
Also published as: CN111417147A

Abstract

The invention discloses a data processing method, a data processing device, related equipment and a storage medium. The method comprises the following steps: when a downlink quality of service flow (QoS flow) is remapped, before the downlink QoS flow is transmitted on a second Data Radio Bearer (DRB), a first Packet Data Convergence Protocol (PDCP) entity of the base station obtains a PDCP Sequence Number (SN) corresponding to a last Service Data Adaptation Protocol (SDAP) Protocol Data Unit (PDU) sent on the first DRB; a first Radio Resource Control (RRC) entity of the base station generates an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN; the first RRC entity sends the RRC connection reconfiguration message to a terminal; the PDCP SN is used to indicate the SN of the last PDCP SDU received by the terminal on the first DRB.

Description

Data processing method, device, related equipment and storage medium

Technical Field

The present invention relates to the field of wireless communications, and in particular, to a data processing method, apparatus, related device, and storage medium.

Background

In the fifth generation mobile communication (5G,Fifth Generation), a service data adaptation protocol (SDAP, service Data Aadaptation Protocol) entity is added in the L2 layer, and the SDAP entity can map and remap quality of service (QoS, quality of Service) flows (flows) with data radio bearers (DRBs, data Resource Bearer).

When the downlink QoS flow is remapped, the base station continues to transmit the downlink QoS flow on the second DRB after the downlink QoS flow is transmitted on the first DRB between the terminal and the base station. The first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow.

When the remapping of the downlink QoS flow occurs, it may happen that the downlink QoS flow packet transmitted at the second DRB reaches the terminal preferentially over the downlink QoS flow packet transmitted at the first DRB, so the terminal may not be able to forward the Packet Data Convergence Protocol (PDCP) service data unit (SDU, service Data Unit) received at the first DRB by the old PDCP entity first, and then forward the PDCP SDU received at the second DRB by the new PDCP entity, that is, the terminal may not be able to guarantee sequential delivery of PDCP SDUs during remapping.

Disclosure of Invention

In order to solve the existing technical problems, the embodiment of the invention provides a data processing method, a data processing device, related equipment and a storage medium.

The technical scheme of the embodiment of the invention is realized as follows:

the embodiment of the invention provides a data processing method, which comprises the following steps:

When the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on the second DRB, a first PDCP entity of the base station obtains a PDCP SN corresponding to the last SDAP PDU sent on the first DRB; the first DRB is a DRB before the downlink QoS flow is remapped, and the second DRB is a DRB after the downlink QoS flow is remapped;

a first RRC entity of the base station generates an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN;

the first RRC entity sends the RRC connection reconfiguration message to a terminal; the PDCP SN is used to indicate the SN of the last PDCP SDU received by the terminal on the first DRB.

In the above solution, the first PDCP entity of the base station obtains a PDCP SN corresponding to a last SDAP PDU sent on the first DRB, including:

the first SDAP entity of the base station sends the last SDAP PDU on a first DRB and sends a notification message to the first PDCP entity;

and after the first PDCP entity receives the notification message, the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB is recorded.

The first SDAP entity determines the number of SDAP PDUs to be sent on the first DRB before transmission on the second DRB and sends the SDAP PDUs to the first PDCP entity;

and the first PDCP entity determines the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB based on the quantity.

In the above scheme, the method further comprises:

the base station determines a new mapping relation of downlink QoS flow remapping;

the RRC connection reconfiguration message also carries configuration information of the new mapping relation; the configuration information is used for configuring the new mapping relation for the SDAP entity of the terminal.

The embodiment of the invention provides a data processing method, which is applied to a terminal and comprises the following steps:

a second RRC entity of the terminal receives an RRC connection reconfiguration message; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped; the first DRB is a DRB before the downlink QoS flow is remapped;

the second PDCP entity sends indication information to a second SDAP entity of the terminal when determining that the last PDCP SDU transmitted on the first DRB is received by utilizing the PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

In the above solution, the determining, by the second PDCP entity, that the last PDCP SDU transmitted on the first DRB has been received by using the PDCP SN carried in the RRC connection reconfiguration message includes:

the second PDCP entity reorders the received PDCP SDUs in sequence, and compares the maximum SNs corresponding to the PDCP SDUs after the ordered PDCP SDUs with PDCP SNs carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

In the above scheme, the method further comprises:

before the indication information is not received, when receiving the PDCP SDU submitted by the third PDCP entity of the terminal, the second SDAP entity locally caches the PDCP SDU submitted by the third PDCP entity in sequence;

after receiving the indication information and upwardly submitting the PDCP SDU submitted by the second PDCP entity in sequence, the second SDAP entity upwardly submits the PDCP SDU submitted by the third PDCP entity which is locally cached in sequence; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped; and the second DRB is a DRB after the downlink QoS flow is remapped.

In the above scheme, the method further comprises:

the third PDCP entity sequences the received PDCP SDUs;

and delivering the sequenced PDCP SDUs to the second SDAP entity in sequence.

In the above scheme, the method further comprises:

the second RRC entity sends configuration information of a new mapping relation of downlink QoS flow remapping carried in the RRC connection reconfiguration message to the second SDAP entity;

the second SDAP entity uses the new mapping relation by utilizing the configuration information.

An embodiment of the present invention provides a data processing apparatus, including:

the first PDCP entity unit is used for acquiring PDCP SNs corresponding to the last SDAP PDU sent on the first DRB before the downlink QoS flow is transmitted on the second DRB when the downlink QoS flow is remapped; the first DRB is a DRB before the downlink QoS flow is remapped, and the second DRB is a DRB after the downlink QoS flow is remapped;

a first RRC entity unit, configured to generate an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN; the RRC connection reconfiguration message is sent to the terminal; the PDCP SN is used to indicate the SN of the last PDCP SDU received by the terminal on the first DRB.

In the above scheme, the device further includes:

a first SDAP entity unit, configured to send a last SDAP PDU on a first DRB, and send a notification message to the first PDCP entity unit;

correspondingly, the first PDCP entity unit is specifically configured to record PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB after receiving the notification message.

In the above solution, the first SDAP entity unit is further configured to determine, before transmission on the second DRB, the number of SDAP PDUs to be sent on the first DRB, and send the number of SDAP PDUs to the first PDCP entity;

correspondingly, the first PDCP entity unit is specifically configured to determine, after receiving the number of the SDAP PDUs sent by the first SDAP entity, a PDCP SN corresponding to a last SDAP PDU sent by the first SDAP entity on the first DRB based on the number; the number is the number of SDAP PDUs to be sent on the first DRB before the first SDAP entity determines to transmit on the second DRB.

An embodiment of the present invention provides a data processing apparatus, including: a second RRC entity unit, a second PDCP entity unit and a second SDAP entity unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

The second RRC entity unit is configured to receive an RRC connection reconfiguration message; and transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity unit of the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped; the first DRB is a DRB before the downlink QoS flow is remapped;

the second PDCP entity unit is configured to send indication information to a second SDAP entity unit when determining that the last PDCP SDU transmitted on the first DRB has been received by using a PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

In the above scheme, the second PDCP entity unit is specifically configured to reorder the received PDCP SDUs in sequence, and compare the maximum SN corresponding to the PDCP SDUs after ordered in sequence with the PDCP SN carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

In the above scheme, the device further includes: a third PDCP entity unit;

The second SDAP entity unit is configured to buffer, when receiving the PDCP SDU submitted by the third PDCP entity unit before receiving the indication information, the PDCP SDU submitted by the third PDCP entity unit in sequence locally; the method is also used for upwardly submitting the PDCP SDU submitted by the third PDCP entity unit which is locally cached in sequence after receiving the indication information and upwardly submitting the PDCP SDU submitted by the second PDCP entity unit in sequence; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped; and the second DRB is a DRB after the downlink QoS flow is remapped.

An embodiment of the present invention provides a base station, including: a first processor and a first communication interface; wherein, the liquid crystal display device comprises a liquid crystal display device,

when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on a second DRB, a first PDCP entity of the base station obtains a PDCP SN corresponding to the last SDAP PDU sent on the first DRB through the first processor; a first RRC entity of the base station generates an RRC connection reconfiguration message through the first processor; the RRC connection reconfiguration message carries the PDCP SN; the first DRB is a DRB before the downlink QoS flow is remapped, and the second DRB is a DRB after the downlink QoS flow is remapped;

The first RRC entity sends the RRC connection reconfiguration message to the terminal through a first communication interface; the PDCP SN is used to indicate the SN of the last PDCP SDU received by the terminal on the first DRB.

In the above scheme, after the first SDAP entity of the base station sends the last SDAP PDU on the first DRB, a notification message is sent to the first PDCP entity through the first communication interface;

after the first PDCP entity receives the notification message through the first communication interface, recording a PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB.

In the above solution, after determining the number of the SDAP PDUs to be sent on the first DRB before the first SDAP entity transmits the first SDAP PDU on the second DRB, the first SDAP entity sends the number to the first PDCP entity through the first communication interface;

after the first PDCP entity receives the number, determining, by the first processor, a PDCP SN corresponding to a last SDAP PDU sent by the first SDAP entity on the first DRB based on the number.

The embodiment of the invention provides a terminal, which comprises: a second processor and a second communication interface; wherein, the liquid crystal display device comprises a liquid crystal display device,

A second RRC entity of the terminal receives an RRC connection reconfiguration message through a second communication interface; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped; the first DRB is a DRB before the downlink QoS flow is remapped;

the second PDCP entity sends indication information to a second SDAP entity of the terminal through the second communication interface when determining that the last PDCP SDU transmitted on the first DRB is received by using the PDCP SN carried in the RRC connection reconfiguration message through a second processor; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

In the above scheme, the second PDCP entity reorders the received PDCP SDUs in sequence through the second processor, and compares the maximum SN corresponding to the PDCP SDUs after the sequence ordering with the PDCP SN carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

In the above scheme, before the indication information is not received, when receiving the PDCP SDU submitted by the third PDCP entity of the terminal, the second SDAP entity locally caches the PDCP SDU submitted by the third PDCP entity in sequence through the second processor;

after receiving the indication information and upwardly submitting the PDCP SDU submitted by the second PDCP entity in sequence, the second SDAP entity upwardly submits the PDCP SDU submitted by the third PDCP entity locally cached in sequence through the second processor in sequence; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped; the second DRB is a DRB after the downlink QoS flow is remapped; .

An embodiment of the present invention provides a base station, including: a first processor and a first memory for storing a computer program capable of running on the first processor,

wherein the first processor is configured to execute the steps of the data processing method described above when the computer program is run.

An embodiment of the present invention provides a terminal, including: a first processor and a second memory for storing a computer program capable of running on the first processor,

An embodiment of the present invention provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the above-described base station side data processing method or implements the steps of the above-described terminal side data processing method.

When downlink QoS flows are remapped, before the downlink QoS flows are transmitted on a second DRB, a first PDCP entity of the base station obtains a PDCP SN corresponding to a last SDAP PDU sent on the first DRB, where the first DRB is a DRB before the downlink QoS flows are remapped, and the second DRB is a DRB after the downlink QoS flows are remapped; the first RRC entity of the base station generates an RRC connection reconfiguration message carrying the PDCP SNs and sends the RRC connection reconfiguration message to the terminal, and the PDCP SNs corresponding to the last SDAP PDU sent on the first DRB are sent to the terminal through the RRC connection reconfiguration message, so that the terminal can determine whether the last PDCP SDU transmitted on the first DRB is received according to the PDCP SNs, that is, the terminal knows that the identification of the last data packet has been transmitted on the first DRB when the downlink QoS flow remapping is performed, the PDCP SDU received on the first DRB can be submitted through the old PDCP entity first, and then the PDCP SDU received on the second DRB can be submitted through the new PDCP entity, and further the data packet can be submitted in sequence in the downlink QoS flow remapping process.

Drawings

FIG. 1 is a flow chart of a data processing method according to an embodiment of the invention;

FIG. 2 is a second flow chart of a data processing method according to an embodiment of the invention;

FIG. 3 is a flowchart illustrating a data processing method according to an embodiment of the present invention;

fig. 4 is a schematic flow chart of implementing sequential delivery when the downlink QoS flow remapping according to the first embodiment is applied;

fig. 5 is a schematic flow chart of implementing sequential delivery when downlink QoS flow remapping according to the second embodiment is applied;

FIG. 6 is a schematic diagram of a data processing apparatus according to an embodiment of the present invention;

FIG. 7 is a schematic diagram showing a second structure of a data processing apparatus according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a composition structure of a base station according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a composition structure of a terminal according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a data processing system according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples.

Two exemplary scenarios of QoS flow remapping are discussed for the SDAP layer in the third generation partnership project (3GPP,the 3rd Generation Partnership Project) radio access network (RAN, radio Access Network) 2 conference, respectively: 1. switching scenes; qos flows are remapped from default DRBs onto the appropriate DRBs.

The design of the SDAP header is also discussed in 3GPP RAN2 conference, namely: the downstream SDAP packet header consists of a 1-bit reflected Qos indication (RQI, reflective Qos Indication), a 1-bit reflected Qos Flow and DRB mapping indication (RDI, reflective Qos Flow to DRB Indication), and a 6-bit quality of service Flow identification (QFI, qos Flow ID); the upstream SDAP packet header consists of 2-bit reserved bits R and 6-bit QFI. Both the upstream SDAP header and the downstream SDAP header are controlled to be 1 byte (byte).

How to guarantee sequential delivery of data packets during uplink QoS flow remapping is also discussed in 3GPP RAN2, 101 th meeting, namely: an end/start identification (marker) mechanism is introduced at the UE side, so that when the packet retransmission occurs in RLC AM mode, sequential delivery of uplink data at the receiving end (i.e., the network side) can be ensured. The end/start marker can be carried by using a reserved bit R in the uplink packet header; a new uplink SDAP control PDU may also be designed to carry, both of which carry end/start marker via the data plane.

Currently, the downlink QoS flow is remapped, and in the radio link control (RLC, radio Link Control) acknowledged (AM, acknowledged Mode) mode or when the physical layer causes the packet retransmission, the downlink QoS flow packet transmitted by the second DRB may reach the terminal preferentially over the downlink QoS flow packet transmitted by the first DRB, and since the terminal cannot determine whether the last packet is already transmitted on the first DRB, it may not be guaranteed that the PDCP SDU received by the first DRB is delivered completely, and then the PDCP SDU received by the second DRB is delivered, that is, the terminal may not be guaranteed to deliver the PDCP SDU sequentially in the remapping process.

Based on this, in the embodiment of the present invention, when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on the second DRB, the first PDCP entity of the base station obtains the PDCP SN corresponding to the last SDAP PDU sent on the first DRB, where the first DRB is the DRB before the downlink QoS flow is remapped, and the second DRB is the DRB after the downlink QoS flow is remapped; and the first RRC entity of the base station generates an RRC connection reconfiguration message carrying the PDCP SN and sends the RRC connection reconfiguration message to the terminal.

According to the scheme provided by the embodiment of the invention, as the PDCP SN corresponding to the last SDAP PDU sent on the first DRB is sent to the terminal through the RRC connection reconfiguration message, the terminal can determine whether the last PDCP SDU transmitted on the first DRB is received or not according to the PDCP SN, that is, the terminal knows the identification of the last data packet transmitted on the first DRB when the downlink QoS flow remapping is finished, namely the identification of the data packet begins to be transmitted on the second DRB, the PDCP SDU received on the first DRB can be submitted through the old PDCP entity firstly and then the PDCP SDU received on the second DRB can be submitted through the new PDCP entity, and further the sequential data packet submission can be realized in the downlink QoS flow remapping process; the first DRB is a DRB before the downlink QoS flow is remapped, and the second DRB is a DRB after the downlink QoS flow is remapped.

An embodiment of the present invention provides a data processing method, applied to a base station, as shown in fig. 1, where the method includes:

step 101: when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on the second DRB, the first PDCP entity of the base station obtains the PDCP SN corresponding to the last SDAP PDU sent on the first DRB.

The first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow.

Here, in the 5G system, the base station may be a next generation node B (gNB).

The remapping of the downlink QoS flow may refer to that the mapping relationship between the downlink QoS flow and the DRB is changed, that is, the downlink QoS flow is remapped from the first DRB to the second DRB.

The PDCP SN may be used as an identifier, specifically, may refer to an identifier that the data packet is transmitted at the end of the first DRB, an identifier that the data packet is transmitted at the beginning of the second DRB, and so on.

When the scheme of the embodiment of the invention is actually applied to a 5G system, the first PDCP entity of the base station can passively determine the PDCP SN; the passive determination of the PDCP SN may refer to that, in the process of remapping the downlink QoS flow from the first DRB to the second DRB, when the first SDAP entity sends the last SDAP PDU on the first DRB, the first PDCP entity may be notified to record the PDCP SN corresponding to the last SDAP PDU.

Based on this, in an embodiment, before the first PDCP entity of the base station obtains the downlink QoS flow for transmission on the second DRB, the PDCP SN corresponding to the last SDAP PDU sent on the first DRB includes: the first SDAP entity of the base station sends the last SDAP PDU on a first DRB and sends a notification message to the first PDCP entity; and after the first PDCP entity receives the notification message, the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB is recorded.

Here, the first SDAP entity informs the first PDCP entity of recording a PDCP SN corresponding to the last SDAP PDU transmitted on the first DRB through the notification message. The PDCP SN may be recorded as an identifier for ending transmission of a packet at the first DRB, and also as an identifier for starting transmission of a packet at the second DRB.

When the scheme of the embodiment of the invention is actually applied to a 5G system, the first PDCP entity of the base station can actively determine the PDCP SN; the actively determining the PDCP SN may refer to, when the first SDAP learns the number of SDAP PDUs to be sent on the first DRB in the process of remapping the downlink QoS flow from the first DRB to the second DRB, sending the number to the first PDCP entity, so that the first PDCP entity calculates the PDCP SN corresponding to the last SDAP PDU.

Based on this, in an embodiment, the PDCP SN of the last SDAP PDU sent on the first DRB before the first PDCP entity of the base station obtains the downlink QoS flow for transmission on the second DRB includes: the first SDAP entity determines the number of SDAP PDUs to be sent on the first DRB before transmission on the second DRB and sends the SDAP PDUs to the first PDCP entity; and the first PDCP entity determines the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB based on the quantity.

Here, the first SDAP entity may notify the first PDCP entity of the number of the SDAP PDUs to be transmitted on the first DRB when knowing that the number is N according to the actual situation, and the first PDCP entity may calculate a PDCP SN corresponding to the last SDAP PDU transmitted on the first DRB based on the number. The calculated PDCP SN may be used as an identifier for ending transmission of a packet at the first DRB and also as an identifier for starting transmission of a packet at the second DRB.

Step 102: a first RRC entity of the base station generates an RRC connection reconfiguration message;

here, the RRC connection reconfiguration message carries the PDCP SN.

After the downlink QoS flow is remapped, and the first PDCP entity determines the PDCP SN corresponding to the last SDAP PDU sent on the first DRB, the first RRC entity may generate an RRC connection reconfiguration message, and carry the PDCP SN in the RRC connection reconfiguration message. The PDCP SN may be used as an identifier, specifically, an identifier that the first DRB ends transmitting the data packet, or an identifier that the second DRB starts transmitting the data packet.

Here, the PDCP SN is carried in the RRC connection reconfiguration message, i.e., by signaling.

Step 103: the first RRC entity sends the RRC connection reconfiguration message to the terminal.

Here, the PDCP SN is used to indicate the SN of the last PDCP PDU received by the terminal on the first DRB.

Here, in the embodiment of the present invention, the name and the location of the PDCP SN in the RRC connection reconfiguration message are not limited, for example, the name may be startmark, and the location may be in a ca-BandwidthClassDL field of the RRC connection reconfiguration message.

When the scheme of the embodiment of the invention is actually applied to a 5G system, if the downlink QoS flow is remapped, the base station can determine a new mapping relation of the downlink QoS flow remapping. The base station may send the new mapping relationship to the terminal, so that the terminal configures the new mapping relationship for its own SDAP entity.

Based on this, in an embodiment, the method further comprises: the base station determines a new mapping relation of downlink QoS flow remapping; the RRC connection reconfiguration message also carries configuration information of the new mapping relation; the configuration information is used for configuring the new mapping relation for the SDAP entity of the terminal.

Here, the first RRC entity sends configuration information carrying the new mapping relation to the terminal, so that the SDAP entity of the terminal may use the new mapping relation by using the configuration information of the new mapping relation.

When the scheme of the embodiment of the invention is actually applied to a 5G system, if the downlink QoS flow is remapped, for example, the downlink QoS flow is remapped from the first DRB to the second DRB, the base station can determine the configuration information of a new PDCP entity of the terminal side of the downlink QoS flow remapping and send the configuration information to the terminal so that the terminal configures the new PDCP entity.

Based on this, in an embodiment, the method further comprises: the base station determines configuration information of a new PDCP entity corresponding to the terminal by a second DRB when the downlink QoS flow is remapped; the RRC connection reconfiguration message also carries configuration information of the new PDCP entity; the configuration information is used for configuring a new PDCP entity for the terminal.

The first RRC entity sends the configuration information carrying the new PDCP entity to the terminal, so that the terminal can configure the new PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

Correspondingly, the embodiment of the invention also provides a data processing method, which is applied to the terminal, as shown in fig. 2, and comprises the following steps:

step 201: a second RRC entity of the terminal receives an RRC connection reconfiguration message; and sending the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal.

The PDCP SN may be used as an identifier, specifically, may refer to an identifier that the last data packet has been transmitted on the first DRB, or an identifier that the data packet starts to be transmitted on the second DRB. The first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow.

Here, the second RRC entity of the terminal may receive the RRC connection reconfiguration message sent by the first RRC entity of the base station, and notify the PDCP SN carried in the RRC connection reconfiguration message to the second PDCP entity of the terminal through interlayer interaction. The second PDCP entity of the terminal is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped. The remapping of the downlink QoS flow may refer to that the mapping relationship between the downlink QoS flow and the DRB is changed, i.e. the downlink QoS flow is remapped from the first DRB to the second DRB.

In a 5G system, the base station may be a next generation node B (gNB).

Step 202: and the second PDCP entity sends indication information to a second SDAP entity of the terminal when determining that the last PDCP SDU transmitted on the first DRB is received by utilizing the PDCP SN carried in the RRC connection reconfiguration message.

The indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

Here, the PDCP SN corresponding to the last SDAP PDU transmitted on the first DRB is transmitted to the terminal through the RRC connection reconfiguration message, so that the terminal can determine whether the last PDCP SDU transmitted on the first DRB has been received according to the PDCP SN.

Based on this, in an embodiment, the determining, by the second PDCP entity, that the last PDCP SDU transmitted on the first DRB has been received using the PDCP SN carried in the RRC connection reconfiguration message includes: the second PDCP entity reorders the received PDCP SDUs in sequence, and compares the maximum SNs corresponding to the PDCP SDUs after the ordered PDCP SDUs with PDCP SNs carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

The reason why the second PDCP entity reorders the received PDCP SDUs in order is: considering that the packet retransmission may occur in the RLC AM mode and the packet retransmission may also occur in the physical layer, the second PDCP entity needs to reorder PDCP SDUs transmitted on the received first DRB in order to find the maximum SN after receiving a packet from the RLC entity of the terminal.

Wherein, the reordering in sequence may mean that after reordering all PDCP SDU data packets in sequence, SN corresponding to each PDCP SDU is a continuous series of digital sequence numbers, and at this time, the maximum SN can be determined; if the SNs corresponding to the PDCP SDUs are not a continuous string of numerical sequence numbers, the maximum SNs cannot be determined.

For example, assuming that after the second PDCP entity reorders all received PDCP SDU data packets in sequence, SN corresponding to each PDCP SDU is 1, 2, 3, 4, 5, the maximum SN is 5; assuming that the corresponding SN of each PDCP SDU is 1, 2, 3, 5, the maximum SN cannot be determined.

Considering that when the downlink QoS flow is remapped, it may happen that the downlink QoS flow packet transmitted in the second DRB reaches the terminal preferentially to the downlink QoS flow packet transmitted in the first DRB, so before the second SDAP entity does not receive the indication message, it is possible to receive the PDCP SDU submitted by the third PDCP entity of the terminal, which may be only buffered and not submitted.

Based on this, in an embodiment, the method further comprises: when receiving the PDCP SDU submitted by the third PDCP entity of the terminal, the second SDAP entity locally caches the PDCP SDU submitted by the third PDCP entity in sequence.

Wherein, the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

Here, when the second SDAP entity does not receive the indication message, even if receiving the PDCP SDU submitted by the third PDCP entity of the terminal, the second SDAP entity performs the sequential buffering process locally, which obviously can avoid the occurrence of a situation that the data packet transmitted on the first DRB is submitted without the data packet transmitted on the second DRB being submitted.

If the second SDAP entity receives the indication message, the old mapping relation between the downlink QoS flow and the DRB is not used any more, after the PDCP SDU received on the first DRB is submitted, the PDCP SDU received on the second DRB is submitted, and meanwhile, the second PDCP entity is released.

Based on this, in an embodiment, the method further comprises: after the PDCP SDU submitted by the second PDCP entity is submitted upwards, the second SDAP entity submits upwards the PDCP SDU submitted by the third PDCP entity, which is locally cached in sequence; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

The second SDAP entity can actively determine or passively determine whether the last data packet transmitted on the first DRB has been transmitted. The passive determination may be that the second SDAP entity determines whether the last data packet transmitted on the first DRB has been transmitted according to the indication message sent by the second PDCP entity. The proactive determination may refer to the second SDAP entity determining, according to a comparison result of the PDCP SN and the maximum SN, whether the last data packet transmitted on the first DRB has been transmitted.

When the second SDAP entity passively determines that the last data packet transmitted on the first DRB is already transmitted after receiving the indication message, the second SDAP entity can sequentially submit SDAP SDUs received on the first DRB to the upper layer and then continue to submit SDAP SDUs received on the second DRB.

When the active determination is performed, the second RRC entity may send the PDCP SN carried in the RRC connection reconfiguration message to the second SDAP entity, and the second PDCP sends the determined maximum SN to the second SDAP entity, so that after the second SDAP entity receives the indication message, the second SDAP entity may compare the maximum SN with the PDCP SN; when the maximum SN is determined to be greater than or equal to the PDCP SN, the last data packet transmitted on the first DRB can be determined to be transmitted, so that the second SDAP entity can continue to submit the SDAP SDU received on the second DRB after sequentially submitting the SDAP SDU received on the first DRB to the upper layer.

In an embodiment, the method further comprises: the third PDCP entity sequences the received PDCP SDUs; and delivering the sequenced PDCP SDUs to the second SDAP entity in sequence.

Here, the third PDCP entity may reorder PDCP SDUs, which are transmitted on the second DRB, in order; and delivering the reordered PDCP SDUs to the second SDAP entity in sequence.

Based on this, in an embodiment, the method further comprises: the second RRC entity sends configuration information of a new mapping relation of downlink QoS flow remapping carried in the RRC connection reconfiguration message to the second SDAP entity; the second SDAP entity uses the new mapping relation by utilizing the configuration information.

By adopting the technical scheme of the embodiment of the invention, the first RRC entity sends the RRC connection reconfiguration message carrying the PDCP SNs to the terminal, and the PDCP SNs corresponding to the last SDAP PDU sent on the first DRB are sent to the terminal through the RRC connection reconfiguration message, so that the terminal can determine whether the last PDCP SDU transmitted on the first DRB is received or not according to the PDCP SNs, that is, the terminal acquires the identification of starting to transmit the data packet on the second DRB when QoS flow remapping is known, and can firstly submit the PDCP SDU received on the first DRB through the old PDCP entity and then submit the PDCP SDU received on the second DRB through the new PDCP entity, thereby realizing sequential data packet submission in the downlink QoS flow remapping process.

An embodiment of the present invention provides a data processing method, as shown in fig. 3, where the method includes:

step 301: when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on the second DRB, the first PDCP entity of the base station obtains the PDCP SN corresponding to the last SDAP PDU sent on the first DRB.

Here, in the 5G system, the base station may be a next generation node B (gNB).

Step 302: a first RRC entity of the base station generates an RRC connection reconfiguration message, wherein the RRC connection reconfiguration message carries the PDCP SN; and transmitting the RRC connection reconfiguration message to the terminal. The PDCP SNs are used for indicating the SN of the last PDCP PDU received by the terminal on the first DRB

Step 303: a second RRC entity of the terminal receives an RRC connection reconfiguration message; and sending the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal.

Step 304: and the second PDCP entity sends indication information to a second SDAP entity of the terminal when determining that the last PDCP SDU transmitted on the first DRB is received by utilizing the PDCP SN carried in the RRC connection reconfiguration message.

It should be noted that: the specific processing procedures of the base station and the terminal are described in detail above, and are not described in detail here.

The first PDCP entity of the base station obtains PDCP SN corresponding to the last SDAP PDU sent on the first DRB; a first RRC entity of the base station generates an RRC connection reconfiguration message, wherein the RRC connection reconfiguration message carries the PDCP SN; and transmitting the RRC connection reconfiguration message to the terminal; a second RRC entity of the terminal receives an RRC connection reconfiguration message; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal; and the second PDCP entity sends indication information to a second SDAP entity of the terminal when determining that the last PDCP SDU transmitted on the first DRB is received by utilizing the PDCP SN carried in the RRC connection reconfiguration message. In this way, when the downlink QoS flow remapping is performed, the terminal knows that the identifier of the last data packet transmitted on the first DRB is obtained when the downlink QoS flow remapping is performed, so that it can be ensured that PDCP SDUs received on the first DRB are submitted first, PDCP SDUs received on the second DRB are submitted through the new PDCP entity, and further, sequential data packet submission can be performed in the downlink QoS flow remapping process.

Embodiments of the present invention will be described in further detail below in conjunction with application examples.

Application example one

In this application embodiment, the downlink QoS flow remapping scenario is: the terminal does not switch, i.e. the downlink QoS flow remapping occurs in one of the SDAP entities. When the downlink QoS flow is remapped, the base station carries the PDCP SN in the RRC connection reconfiguration message and sends the PDCP SN to the terminal, so that the terminal knows that the identification of the last data packet is transmitted on the first DRB when the downlink QoS flow is remapped, and the aim of sequentially submitting the data packets in the downlink QoS flow remapping process can be ensured. The first DRB may be a DRB before the remapping of the downlink QoS flow.

In addition, in this application embodiment, the RRC entity of the network side corresponds to the first RRC entity, the SDAP entity of the network side corresponds to the first SDAP entity, the old PDCP entity of the network side corresponds to the first PDCP entity, the RRC entity of the terminal corresponds to the second RRC entity, the old PDCP entity of the terminal corresponds to the second PDCP entity, and the new PDCP entity of the terminal corresponds to the third PDCP entity.

Fig. 4 is a schematic flow chart of implementing sequential delivery when downlink QoS flow remapping is performed in the present application embodiment, as shown in fig. 4, a process for implementing sequential delivery when downlink QoS flow remapping is performed includes the following steps:

Step 401: when the downlink QoS flow is remapped, the RRC entity at the network side configures a new mapping relation between the downlink QoS flow and the DRB.

Step 402: the SDAP entity of the network sends the Last SDAP PDU (which can be expressed as Last SDAP PDU) on the first DRB, and sends a notification message to the Old PDCP (which can be expressed as Old PDCP) entity of the network side.

Here, the first SDAP entity may also determine the number of SDAP PDUs to be transmitted on the first DRB before transmission on the second DRB, and transmit to the first PDCP entity; the second DRB may be a DRB after the downlink QoS flow is remapped.

Step 403: after receiving the notification message, the Old PDCP entity of the network side records the PDCP SN corresponding to the last SDAP PDU sent on the first DRB.

Here, the first PDCP entity may further determine a PDCP SN corresponding to a last SDAP PDU transmitted by the first SDAP entity on the first DRB based on the number transmitted by the first SDAP entity.

Step 404: the Old PDCP entity of the network transmits the PDCP SN to the RRC entity of the network side.

Step 405: the RRC entity at the network side generates an RRC connection reconfiguration message (which may be expressed as RRCReconfiguration message); and carrying the PDCP SN in the RRC connection reconfiguration message.

Step 406: the RRC entity of the network side sends the RRC connection reconfiguration message to the RRC entity of the terminal side; the RRC connection reconfiguration message carries the new mapping relation and the PDCP SN.

Step 407: the RRC entity of the terminal side transmits the PDCP SN to a Old PDCP (which may be expressed as Old PDCP) entity of the terminal side.

Step 408: the old PDCP entity at the terminal side reorders the received PDCP SDUs in sequence, takes the SN corresponding to the PDCP SDU with the largest SN in all the PDCP SDUs after the ordered sequence as the largest SN, and compares the largest SN with the PDCP SN carried in the RRC connection reconfiguration message; and judging whether the maximum SN is larger than or equal to the PDCP SN carried in the RRC connection reconfiguration message.

Step 409: before the SDAP entity of the terminal side does not receive the Indication message (which may be expressed as Indication) sent by the old PDCP entity of the terminal side, the New PDCP (which may be expressed as New PDCP) entity of the terminal side is locally cached in sequence for the PDCP SDU submitted in sequence.

Step 410: when determining that the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, the Old PDCP entity of the terminal side determines that the last PDCP SDU transmitted on the first DRB has been received, and sends an indication message to the SDAP entity of the terminal side.

Step 411: after receiving the indication message, the SDAP entity at the terminal side does not use the old mapping relation between the downlink QoS flow and the DRB any more, and submits SDAP SDU to the upper layer in sequence.

Note that Data is Data transmitted on the first DRB; new data is data transmitted on the second DRB.

And when the downlink QoS flow is remapped, the base station sends the PDCP SN to the terminal through the RRC connection reconfiguration message, so that the terminal obtains the identification that the last data packet is transmitted on the first DRB when the downlink QoS flow is remapped, the PDCP SDU received on the first DRB can be ensured to be submitted first, then the PDCP SDU received on the second DRB is submitted through the new PDCP entity, and further, the sequential data packet delivery can be realized in the downlink QoS flow remapping process.

Application example II

In this application embodiment, the downlink QoS flow remapping scenario is: the terminal is switched from the source base station to the destination base station, i.e. the downlink QoS flow remapping between two SDAP entities. When the downlink QoS flow is remapped, the source base station may send the PDCP SN to the destination base station, so that the destination base station may carry the PDCP SN in the RRC connection reconfiguration message and send the PDCP SN to the terminal, so that the terminal knows that the identifier of the last data packet has been transmitted on the first DRB when the downlink QoS flow is remapped, and can ensure that sequential delivery of the data packets in the downlink QoS flow remapping process is achieved. The first DRB may be a DRB before the remapping of the downlink QoS flow.

In addition, in this application embodiment, the RRC entity of the destination base station corresponds to the first RRC entity, the SDAP entity of the destination base station corresponds to the first SDAP entity, the old PDCP entity of the destination base station corresponds to the first PDCP entity, the RRC entity of the terminal corresponds to the second RRC entity, the old PDCP entity of the terminal corresponds to the second PDCP entity, and the new PDCP entity of the terminal corresponds to the third PDCP entity.

Fig. 5 is a schematic flow chart of implementing sequential delivery when downlink QoS flow remapping is performed in the present application embodiment, and as shown in fig. 5, a process for implementing sequential delivery when downlink QoS flow remapping is performed includes the following steps:

step 501: the Old PDCP (which may be expressed as Old PDCP) entity of the destination base station records PDCP SNs corresponding to the Last SDAP PDU (which may be expressed as Last SDAP PDU) transmitted on the first DRB, which is transmitted by the source base station.

Prior to step 501, the following steps may also be included:

step 5010: and when the downlink QoS flows are remapped, the RRC entity of the source base station configures a new mapping relation between the downlink QoS flows and the DRB.

Step 5011: the SDAP entity of the source base station transmits the last SDAP PDU on the first DRB and transmits a notification message to the Old PDCP (which may be expressed as Old PDCP) entity of the source base station.

Step 5012: after the old PDCP entity of the source base station receives the notification message, the PDCP SN corresponding to the last SDAP PDU sent on the first DRB is recorded, and the PDCP SN is sent to the old PDCP entity of the target base station.

Here, the source base station may also send the new mapping relationship and the old mapping relationship between the downlink QoS flow and the DRB to the destination base station, so that the destination base station may still continue to transmit data to the terminal on the first DRB.

Step 502: the old PDCP entity of the target base station transmits the recorded PDCP SNs to the RRC entity of the target base station.

Step 503: the RRC entity of the destination base station generates an RRC connection reconfiguration message (which may be expressed as RRCReconfiguration message); and carrying the PDCP SN in the RRC connection reconfiguration message.

Step 504: the RRC entity of the target base station sends the RRC connection reconfiguration message to an RRC entity of a terminal side; the RRC connection reconfiguration message carries the new mapping relation and the PDCP SN.

Step 505: the RRC entity of the terminal side transmits the PDCP SN to a Old PDCP (which may be expressed as Old PDCP) entity of the terminal side.

Step 506: the old PDCP entity at the terminal side reorders the received PDCP SDUs in sequence, and compares the maximum SNs corresponding to the reordered PDCP SDUs with the PDCP SNs carried in the RRC connection reconfiguration message; and judging whether the maximum SN is larger than or equal to the PDCP SN carried in the RRC connection reconfiguration message.

Step 507: before the SDAP entity of the terminal side does not receive the Indication message (which can be expressed as Indication) sent by the Old PDCP entity of the terminal side, the PDCP SDUs submitted by the New PDCP entity of the terminal side are locally cached in sequence.

Step 508: when determining that the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, the Old PDCP entity of the terminal side determines that the last PDCP SDU transmitted on the first DRB has been received, and sends an indication message to the SDAP entity of the terminal side.

Step 509: after receiving the indication message, the SDAP entity at the terminal side does not use the old mapping relation between the downlink QoS flow and the DRB any more, and sequentially submits SDAP SDUs to an upper layer.

It should be noted that, forwarded data is data that is continuously transmitted on the first DRB at the destination base station; new data is data transmitted by the destination base station on the second DRB. The second DRB may be a DRB after the downlink QoS flow is remapped.

And when the downlink QoS flow is remapped, the source base station transmits the PDCP SN to the target base station, so that the target base station can transmit the PDCP SN to the terminal through the RRC connection reconfiguration message, the terminal knows that the identification of the last data packet is transmitted on the first DRB when the downlink QoS flow is remapped, the PDCP SDU received on the first DRB can be ensured to be submitted firstly, and then the PDCP SDU received on the second DRB is submitted through a new PDCP entity, so that the sequential data packet delivery can be realized in the downlink QoS flow remapping process.

In order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides a data processing device, which is disposed on a base station, as shown in fig. 6, and the device includes:

a first PDCP entity unit 61, configured to obtain, when remapping occurs on a downlink QoS flow, a PDCP SN corresponding to a last SDAP PDU sent on a first DRB before the downlink QoS flow is transmitted on a second DRB between a terminal and a base station;

a first RRC entity unit 62, configured to generate an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN; the RRC connection reconfiguration message is sent to the terminal; the PDCP SNs are used to indicate the SNs of the last PDCP PDU received by the terminal on the first DRB.

Here, in the 5G system, the base station may be a next generation node B (gNB).

When the scheme of the embodiment of the invention is actually applied to a 5G system, the first PDCP entity of the base station can passively determine the PDCP SN; wherein, the passive determination of the PDCP SN may refer to that the first SDAP entity notifies the first PDCP entity to record the PDCP SN corresponding to the last SDAP PDU.

Based on this, in an embodiment, the device further comprises: the first SDAP entity unit is used for sending the last SDAP PDU on the first DRB and sending a notification message to the first PDCP entity unit; correspondingly, the first PDCP entity unit is specifically configured to record PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB after receiving the notification message.

When the scheme of the embodiment of the invention is actually applied to a 5G system, the first PDCP entity of the base station can actively determine the PDCP SN; the actively determining the PDCP SN may refer to that the first PDCP entity calculates a PDCP SN corresponding to a last SDAP PDU according to the number of SDAP PDUs to be transmitted on the first DRB that are transmitted by the first SDAP entity.

Based on this, in an embodiment, the first SDAP entity unit is further configured to determine, before transmission on the second DRB, a number of SDAP PDUs to be sent on the first DRB, and send the number of SDAP PDUs to the first PDCP entity; correspondingly, the first PDCP entity unit is specifically configured to determine, after receiving the number of the SDAP PDUs sent by the first SDAP entity, a PDCP SN corresponding to a last SDAP PDU sent by the first SDAP entity on the first DRB based on the number; the number is the number of SDAP PDUs to be sent on the first DRB before the first SDAP entity determines to transmit on the second DRB.

Based on this, in an embodiment, the base station may also determine a new mapping relationship for downlink QoS flow remapping. Correspondingly, the first RRC entity is further configured to carry configuration information of the new mapping relationship in the RRC connection reconfiguration message; the configuration information is used for configuring the new mapping relation for the SDAP entity of the terminal.

Based on this, in an embodiment, the base station may further determine configuration information of a new PDCP entity corresponding to the terminal by the second DRB at the time of downlink QoS flow remapping. Correspondingly, the first RRC entity is further configured to carry configuration information of the new PDCP entity in the RRC connection reconfiguration message; the configuration information is used for configuring a new PDCP entity for the terminal.

Here, the base station sends the configuration information carrying the new PDCP entity to the terminal through the first RRC entity unit, so that the terminal may configure the new PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

In practical application, the first PDCP entity unit 61 and the first RRC entity unit 62 may be implemented by a processor in a data processing apparatus.

It should be noted that: in the data processing apparatus provided in the above embodiment, only the division of each program module is used for illustration, and in practical application, the processing allocation may be performed by different program modules according to needs, that is, the internal structure of the apparatus is divided into different program modules, so as to complete all or part of the processing described above. In addition, the data processing apparatus provided in the above embodiment and the data processing method embodiment on the base station side belong to the same concept, and the specific implementation process is detailed in the method embodiment, which is not repeated here.

In order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides a data processing device, which is disposed on a terminal, as shown in fig. 7, and the device includes: a second RRC entity unit 71, a second PDCP entity unit 72, a second SDAP entity unit 73; wherein, the liquid crystal display device comprises a liquid crystal display device,

The second RRC entity unit 71 is configured to receive an RRC connection reconfiguration message; and a second PDCP entity unit 72 for transmitting the PDCP SN carried in the RRC connection reconfiguration message to the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped;

the second PDCP entity unit 72 is configured to send indication information to the second SDAP entity unit 73 when determining that the last PDCP SDU transmitted on the first DRB has been received, using the PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

The PDCP SN may be used as an identifier, specifically, may refer to an identifier that the data packet is transmitted at the end of the first DRB, or an identifier that the data packet is transmitted at the beginning of the second DRB, etc. The first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow.

In a 5G system, the base station may be a next generation node B (gNB).

Based on this, in an embodiment, the second PDCP entity unit 72 is specifically configured to reorder the received PDCP SDUs in sequence, and compare the maximum SN corresponding to the PDCP SDUs in sequence with the PDCP SN carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

Based on this, in an embodiment, the device further comprises: a third PDCP entity unit;

the second SDAP entity unit 73 is configured to buffer, when receiving the PDCP SDU submitted by the third PDCP entity unit before receiving the indication information, the PDCP SDU submitted by the third PDCP entity in sequence locally.

Based on this, in an embodiment, the second SDAP entity unit 73 is further configured to, after receiving the indication information and upwardly submitting the PDCP SDU submitted by the second PDCP entity unit 72, upwardly and sequentially submit the PDCP SDU submitted by the third PDCP entity unit of the local sequential buffer; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

In practical application, the second RRC entity unit 71 may be implemented by a processor in the data processing apparatus in combination with a communication interface; the second PDCP entity unit 72, the second SDAP entity unit 73, the third PDCP entity unit may be implemented by a processor in a data processing apparatus.

It should be noted that: in the data processing apparatus provided in the above embodiment, only the division of each program module is used for illustration, and in practical application, the processing allocation may be performed by different program modules according to needs, that is, the internal structure of the apparatus is divided into different program modules, so as to complete all or part of the processing described above. In addition, the data processing device provided in the above embodiment and the data processing method embodiment on the terminal side belong to the same concept, and the specific implementation process is detailed in the method embodiment, which is not repeated here.

Based on the hardware implementation of each program module, in order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides a base station, as shown in fig. 8, where the base station 80 includes: a first processor 81 and a first communication interface 82; wherein, the liquid crystal display device comprises a liquid crystal display device,

when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on the second DRB, the first PDCP entity of the base station obtains, through the first processor 81, a pdcppsn corresponding to the last SDAP PDU sent on the first DRB; a first RRC entity of the base station generates an RRC connection reconfiguration message through the first processor 81; the RRC connection reconfiguration message carries the PDCP SN;

The first RRC entity sends the RRC connection reconfiguration message to the terminal through the first communication interface 82; the PDCP SN is used to indicate the SN of the last PDCP SDU received by the terminal on the first DRB.

The first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow. The PDCP SN may be used as an identifier, specifically, may refer to an identifier that the data packet is transmitted at the end of the first DRB, an identifier that the data packet is transmitted at the beginning of the second DRB, and so on.

In a 5G system, the base station may be a next generation node B (gNB). The remapping of the downlink QoS flow may refer to a change in a mapping relationship between the downlink QoS flow and the DRB, i.e. remapping the downlink QoS flow from the first DRB to the second DRB.

Based on this, in an embodiment, after the first SDAP entity of the base station has sent the last SDAP PDU on the first DRB, a notification message is sent to the first PDCP entity through the first communication interface 82; after the first PDCP entity receives the notification message through the first communication interface 82, the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB is recorded.

Based on this, in an embodiment, the first SDAP entity determines the number of SDAP PDUs to be sent on the first DRB before transmission on the second DRB, and then sends the number to the first PDCP entity through the first communication interface 82; after the first PDCP entity receives the number, based on the number, the PDCP SN corresponding to the last SDAP PDU sent by the first SDAP entity on the first DRB is determined by the first processor 81.

Based on this, in an embodiment, the base station may also determine a new mapping relationship for downlink QoS flow remapping. Carrying configuration information of the new mapping relation in the RRC connection reconfiguration message; the configuration information is used for configuring the new mapping relation for the SDAP entity of the terminal.

Based on this, in an embodiment, the base station may further determine configuration information of a new PDCP entity corresponding to the terminal by the second DRB at the time of downlink QoS flow remapping. Carrying configuration information of the new PDCP entity in the RRC connection reconfiguration message; the configuration information is used for configuring a new PDCP entity for the terminal.

The specific processing procedure of the first processor 81 may be understood by referring to a method, and will not be described herein.

Of course, in practice, as shown in FIG. 8, the various components in the base station 80 are coupled together by a bus system 84. It is understood that the bus system 84 is used to enable connected communications between these components. The bus system 84 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as bus system 84 in fig. 8.

The first memory 83 in the embodiment of the present invention is used to store various types of data to support the operation of the base station 80. Examples of such data include: any computer program for operation on the base station 80.

The method disclosed in the above embodiment of the present invention may be applied to the first processor 81 or implemented by the first processor 81. The first processor 81 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of integrated logic circuits of hardware or software in the first processor 81. The first processor 81 described above may be a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The first processor 81 may implement or perform the methods, steps and logic blocks disclosed in embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the invention can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the first memory 83, said first processor 81 reading information in the first memory 83, in combination with its hardware performing the steps of the method described above.

In an exemplary embodiment, the base station 80 may be implemented by one or more application specific integrated circuits (ASICs, application Specific Integrated Circuit), DSPs, programmable logic devices (PLDs, programmable Logic Device), complex programmable logic devices (CPLDs, complex Programmable Logic Device), field Programmable Gate Arrays (FPGAs), field-Programmable Gate Array), general purpose processors, controllers, microcontrollers (MCUs, micro Controller Unit), microprocessors (microprocessors), or other electronic elements for performing the aforementioned methods.

Based on the hardware implementation of each program module, in order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides a terminal, as shown in fig. 9, where the terminal 90 includes: a second processor 91 and a second communication interface 92; wherein, the liquid crystal display device comprises a liquid crystal display device,

a second RRC entity of the terminal receives the RRC connection reconfiguration message through the second communication interface 92; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped;

the second PDCP entity sends indication information to a second SDAP entity of the terminal through the second communication interface 92 when determining, through the second processor 91, that the last PDCP SDU transmitted on the first DRB has been received, by using the PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

Wherein, the first DRB may be a DRB before the remapping of the downlink QoS flow, and the second DRB may be a DRB after the remapping of the downlink QoS flow. The PDCP SN may be used as an identifier, specifically, may refer to an identifier that the data packet is transmitted at the end of the first DRB, an identifier that the data packet is transmitted at the beginning of the second DRB, and so on.

In a 5G system, the base station may be a next generation node B (gNB).

Based on this, in an embodiment, the second PDCP entity reorders the received PDCP SDUs in sequence by the second processor 91, and compares the maximum SN corresponding to the PDCP SDUs ordered in sequence with the PDCP SN carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

Based on this, in an embodiment, when receiving PDCP SDUs submitted by the third PDCP entity of the terminal before the indication information is not received, the second SDAP entity locally buffers PDCP SDUs submitted by the third PDCP entity in sequence through the second processor 91;

Based on this, in an embodiment, after receiving the indication information and sequentially submitting the PDCP SDUs submitted by the second PDCP entity upwards, the second SDAP entity sequentially submits the PDCP SDUs submitted by the third PDCP entity locally buffered in sequence upwards through the second processor 91; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped.

The specific processing procedure of the second processor 91 may be understood by referring to a method, and will not be described herein.

Of course, in practical application, the terminal 90 may further include: a user interface 95. As shown in fig. 9, the various components in terminal 90 are coupled together by a bus system 94. It is understood that the bus system 94 is used to enable connected communication between these components. The bus system 94 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as bus system 94 in fig. 9.

Wherein the number of the second processors 91 is at least one.

The user interface 95 may include buttons, a touch pad, or a touch screen, among others.

The second memory 93 in the embodiment of the present invention is used to store various types of data to support the operation of the terminal 90.

The method disclosed in the above embodiment of the present invention may be applied to the second processor 91 or implemented by the second processor 91. The second processor 91 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in software form in the second processor 91. The second processor 91 may be a general purpose processor, DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The second processor 91 may implement or perform the methods, steps and logic blocks disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the invention can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the second memory 93 and the second processor 91 reads information in the second memory 93, in combination with its hardware, performing the steps of the method as described above.

In an exemplary embodiment, the terminal 90 can be implemented by one or more ASIC, DSP, PLD, CPLD, FPGA, general-purpose processors, controllers, MCU, microprocessor, or other electronic elements for performing the foregoing methods.

It will be appreciated that the memories (such as the first memory 83 and the second memory 93) in the embodiments of the present invention may be volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memories. Wherein the nonvolatile Memory may be Read Only Memory (ROM), programmable Read Only Memory (PROM, programmable Read-Only Memory), erasable programmable Read Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable Read Only Memory (EEPROM, electrically Erasable Programmable Read-Only Memory), magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk Read Only Memory (CD-ROM, compact Disc Read-Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The memory described by embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides a data processing system, as shown in fig. 10, where the system includes:

when a downlink QoS flow is remapped, the base station 101 obtains, through a first PDCP entity of itself, a PDCP sequence number SN corresponding to a last service data adaptation protocol SDAP protocol data unit PDU sent on the first DRB, before the downlink QoS flow is transmitted on a new radio data bearer DRB; and generating an RRC connection reconfiguration message through the own first RRC entity; the RRC connection reconfiguration message carries the PDCP SN; and transmitting the RRC connection reconfiguration message to the terminal; the PDCP SN is used to indicate the SN of the last PDCP service data unit SDU received by the terminal on the first DRB.

A terminal 102, configured to receive an RRC connection reconfiguration message through a second RRC entity of the terminal; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity of the PDCP SN; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped; the second PDCP entity utilizes the PDCP SN carried in the RRC connection reconfiguration message to send indication information to the second SDAP entity when determining that the last PDCP SDU transmitted on the first DRB is received; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more.

It should be noted that: the specific functions of the base station 101 and the terminal 102 are also described in detail above, and will not be described again here.

In an exemplary embodiment, the present invention further provides a storage medium, specifically a computer readable storage medium, for example, a first memory 83 including a computer program, where the computer program may be executed by the first processor 81 of the base station 80 to perform the steps of the foregoing base station side method, or a second memory 93 including a computer program, where the computer program may be executed by the second processor 91 of the terminal 90 to perform the steps of the foregoing network device side method.

The computer readable storage medium may be FRAM, ROM, PROM, EPROM, EEPROM, flash Memory, magnetic surface Memory, optical disk, or CD-ROM.

It should be noted that: "first," "second," etc. are used to distinguish similar objects and not necessarily to describe a particular order or sequence.

It should be noted that: the technical schemes described in the embodiments of the present invention may be arbitrarily combined without any collision.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A data processing method, applied to a base station, the method comprising:

when the downlink QoS flow is remapped, before the downlink QoS flow is transmitted on a second wireless data bearer (DRB), a first Packet Data Convergence Protocol (PDCP) entity of the base station obtains a PDCP Serial Number (SN) corresponding to a last Service Data Adaptation Protocol (SDAP) Protocol Data Unit (PDU) transmitted on the first DRB; the first DRB is a DRB before the downlink QoS flow is remapped, and the second DRB is a DRB after the downlink QoS flow is remapped;

a first Radio Resource Control (RRC) entity of the base station generates an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN;

the first RRC entity sends the RRC connection reconfiguration message to a terminal; the PDCP SN is used for indicating the SN of the last PDCP service data unit SDU received by the terminal on the first DRB;

wherein the method further comprises:

when the downlink QoS flow is remapped, the RRC entity of the base station configures a new mapping relation between the downlink QoS flow and the DRB;

the SDAP entity of the base station sends a last SDAP PDU on a first DRB and sends a notification message to a first PDCP entity of the base station;

After receiving the notification message, the first PDCP entity of the base station records the PDCP SN corresponding to the last SDAP PDU sent on the first DRB;

the first PDCP entity of the base station transmits the PDCP SN to the RRC entity of the base station;

the RRC entity of the base station generates an RRC connection reconfiguration message; and carrying the PDCP SN in the RRC connection reconfiguration message.

2. The method of claim 1 wherein the first PDCP entity of the base station obtains a PDCP SN corresponding to a last SDAP PDU sent on the first DRB, comprising:

3. The method of claim 1 wherein the first PDCP entity of the base station obtains a PDCP SN corresponding to a last SDAP PDU sent on the first DRB, comprising:

the first SDAP entity of the base station determines the number of SDAP PDUs to be sent on the first DRB before being transmitted on the second DRB, and sends the SDAP PDUs to the first PDCP entity;

4. The method according to claim 1, wherein the method further comprises:

5. A data processing method, applied to a terminal, the method comprising:

the second PDCP entity sends indication information to a second SDAP entity of the terminal when determining that the last PDCP SDU transmitted on the first DRB is received by utilizing the PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more;

Wherein, the liquid crystal display device comprises a liquid crystal display device,

6. The method of claim 5 wherein the second PDCP entity utilizing the PDCP SN carried in the RRC connection reconfiguration message determines the last PDCP SDU that has been received for transmission on the first DRB comprises:

7. The method of claim 5, wherein the method further comprises:

8. The method of claim 7, wherein the method further comprises:

the third PDCP entity sequences the received PDCP SDUs;

and delivering the sequenced PDCP SDUs to the second SDAP entity in sequence.

9. The method of claim 5, wherein the method further comprises:

10. A data processing apparatus, the apparatus comprising:

a first RRC entity unit, configured to generate an RRC connection reconfiguration message; the RRC connection reconfiguration message carries the PDCP SN; the RRC connection reconfiguration message is sent to the terminal; the PDCP SN is used for indicating the SN of the last PDCP SDU received by the terminal on the first DRB;

11. The apparatus of claim 10, wherein the apparatus further comprises:

12. The apparatus of claim 10, wherein the device comprises a plurality of sensors,

the first SDAP entity unit is further configured to determine, before transmission on the second DRB, the number of SDAP PDUs to be sent on the first DRB, and send the SDAP PDUs to the first PDCP entity;

13. A data processing apparatus, the apparatus comprising: a second RRC entity unit, a second PDCP entity unit and a second SDAP entity unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the second RRC entity unit is configured to receive an RRC connection reconfiguration message; transmitting the PDCP SN carried in the RRC connection reconfiguration message to a second PDCP entity unit of the terminal; the second PDCP entity is the PDCP entity corresponding to the first DRB when the downlink QoS flow is remapped; the first DRB is a DRB before the downlink QoS flow is remapped;

the second PDCP entity unit is configured to send indication information to a second SDAP entity unit when determining that the last PDCP SDU transmitted on the first DRB has been received by using a PDCP SN carried in the RRC connection reconfiguration message; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more;

14. The apparatus of claim 13, wherein the device comprises a plurality of sensors,

the second PDCP entity unit is specifically configured to reorder the received PDCP SDUs in sequence, and compare the maximum SN corresponding to the PDCP SDUs after ordered with the PDCP SN carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

15. The apparatus of claim 13, wherein the apparatus further comprises: a third PDCP entity unit;

16. A base station, the base station comprising: a first processor and a first communication interface; wherein, the liquid crystal display device comprises a liquid crystal display device,

the first RRC entity sends the RRC connection reconfiguration message to the terminal through a first communication interface; the PDCP SN is used for indicating the SN of the last PDCP SDU received by the terminal on the first DRB;

17. The base station of claim 16, wherein the base station,

after the first SDAP entity of the base station sends the last SDAP PDU on the first DRB, sending a notification message to the first PDCP entity through the first communication interface;

18. The base station of claim 16, wherein the base station,

the first SDAP entity of the base station determines the number of SDAP PDUs to be sent on the first DRB before transmission on the second DRB, and then sends the number to the first PDCP entity through the first communication interface;

19. A terminal, the terminal comprising: a second processor and a second communication interface; wherein, the liquid crystal display device comprises a liquid crystal display device,

the second PDCP entity sends indication information to a second SDAP entity of the terminal through the second communication interface when determining that the last PDCP SDU transmitted on the first DRB is received by using the PDCP SN carried in the RRC connection reconfiguration message through a second processor; the indication information is used for indicating that the second SDAP entity does not use the old mapping relation between the downlink QoS flow and the DRB any more;

20. The terminal of claim 19, wherein the terminal comprises a base station,

the second PDCP entity reorders the received PDCP SDUs in sequence through the second processor, and compares the largest SN corresponding to the PDCP SDUs after the ordered PDCP SDUs with the PDCP SNs carried in the RRC connection reconfiguration message; and when the maximum SN is greater than or equal to the PDCP SN carried in the RRC connection reconfiguration message, determining that the last PDCP SDU transmitted on the first DRB is received.

21. The terminal of claim 19, wherein the terminal comprises a base station,

before the indication information is not received, when receiving the PDCP SDU submitted by the third PDCP entity of the terminal, the second SDAP entity locally caches the PDCP SDU submitted by the third PDCP entity in sequence through the second processor;

After receiving the indication information and upwardly submitting the PDCP SDU submitted by the second PDCP entity in sequence, the second SDAP entity upwardly submits the PDCP SDU submitted by the third PDCP entity locally cached in sequence through the second processor in sequence; the third PDCP entity is a PDCP entity corresponding to the second DRB when the downlink QoS flow is remapped; and the second DRB is a DRB after the downlink QoS flow is remapped.

22. A base station, comprising: a first processor and a first memory for storing a computer program capable of running on the first processor,

wherein the first processor is adapted to perform the steps of the method of any of claims 1 to 4 when the computer program is run.

23. A terminal, comprising: a first processor and a second memory for storing a computer program capable of running on the first processor,

wherein the first processor is adapted to perform the steps of the method of any of claims 5 to 9 when the computer program is run.

24. A storage medium having stored thereon a computer program, which when executed by a processor, performs the steps of the method of any of claims 1 to 4 or performs the steps of the method of any of claims 5 to 9.