CN110536487B

CN110536487B - Data transmission method and device

Info

Publication number: CN110536487B
Application number: CN201811015695.5A
Authority: CN
Inventors: 徐海博; 袁锴; 崔立伟; 金辉; 方平; 庄宏成
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-05-25
Filing date: 2018-08-31
Publication date: 2021-12-10
Anticipated expiration: 2038-08-31
Also published as: CN110536487A

Abstract

The application relates to the technical field of communication, and discloses a data transmission method and device, which are used for reducing uplink data transmission delay of a DRB. The method comprises the following steps: a terminal performs uplink data transmission on a DRB, wherein the DRB is a first bearer type, a PDCP entity of the first bearer type is configured to associate an RLC entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, the first cell group belongs to a first network device, and the second cell group belongs to a second network device; and when the terminal determines that the accessed second cell group is unavailable, the type of the DRB is converted from the first bearer type to a second bearer type, and the PDCP entity of the second bearer type is only associated with the RLC entity corresponding to the first cell group.

Description

Data transmission method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data transmission method and device.

Background

With the continuous development and improvement of New Radio (NR) of 5G, NR has gradually moved to commercial use, and in order to ensure the stability of data transmission, in the early stage of NR deployment, a Dual Connectivity (DC) networking mode will be the networking mode selected by most operators. The networking mode of dual connectivity existing in 5G applications includes: (1) the method comprises the following steps of an ED-DC networking mode, namely a terminal is connected to a 4G LTE base station and a 5G NR base station at the same time, wherein the NR base station is called an En-gNB and the LTE base station is called an eNB under the EN-DC networking mode, the LTE base station is a main base station/node and is also called an MeNB in the EN-DC, the NR base station is an auxiliary base station/node and is also called an SgNB in the EN-DC; (2) in the EN-DC networking mode, the NR base station is called gNB, the LTE base station is called eNB, wherein the NR base station is a main base station/node, and is also called MgNB in the NE-DC; eNB is a secondary base station/node, also known as SeNB in NE-DC; (3) in the NGEN-DC networking mode, a terminal is simultaneously connected with a 4G LTE base station and a 5G NR base station, wherein the NR base station is called gNB and the LTE base station is called ng-eNB in the NGEN-DC networking mode, wherein the NR base station is a main base station/node and is also called MeNB in the NGEN-DC; the LTE base station is an auxiliary base station/node, is also called SgNB in the NGEN-DC, and is different from the connection establishment of an NR base station and a 4G core network in an EN-DC networking mode, in the NGEN-DC networking mode, the LTE base station is connected with the 5G core network; (4) in the NR-NR DC networking mode, a terminal is simultaneously connected to two 5G NR base stations, and in the NR-NR DC networking mode, the NR base stations are called gnbs, where one NR base station is a main base station/node, i.e., an MgNB; another NR base station is a secondary base station/node, SgNB.

In the data transmission process of the dual connection, if a Data Radio Bearer (DRB) of the terminal is configured as a Split (Split) bearer, the terminal, when detecting that a cell or a cell group under a secondary base station is unavailable, may send a radio resource control layer message to a primary base station, and then wait for a Radio Resource Control (RRC) connection reconfiguration message sent by the primary base station, and the primary base station may reserve a configuration of a cell group (SCG) under the secondary base station for the DRB or release a configuration of the SCG for the DRB, but the primary base station may convert the Split bearer of the DRB into a cell group (MCG) bearer under the primary base station through the RRC connection reconfiguration message, so as to convert an uplink data transmission path of the DRB into MCG transmission only. However, in the prior art, the terminal must perform the conversion from the Split bearer of the DRB to the MCG bearer after receiving the RRC connection reconfiguration message, and further convert the uplink transmission path of the DRB to only transmit through the MCG, which results in a long time for interrupting the uplink data transmission of the DRB and a long time delay.

Disclosure of Invention

The embodiment of the application provides a data transmission method and device, which are used for solving the problem of long time delay caused by overlong uplink data transmission interruption time of a DRB (distributed radio service) when Split bearer switching is carried out under a dual-connection networking.

In a first aspect, a data transmission method is provided, in which a terminal performs uplink data transmission on a DRB, where a Packet Data Convergence Protocol (PDCP) entity of the DRB is configured to associate a Radio Link Control (RLC) entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, the first cell group belongs to a first network device, and the second cell group belongs to a second network device; and when the terminal determines that the accessed second cell group is unavailable, configuring the PDCP entity of the DRB to be only associated with the RLC entity corresponding to the first cell group. Through the data transmission method, if the DRB of the terminal is configured to perform uplink data transmission through the first cell group belonging to the first network device and the second cell group belonging to the second network device, when the terminal determines that the second cell group of the accessed second network device is unavailable, the DRB is directly configured to perform uplink data transmission through the first cell group belonging to the first network device without sending a radio resource control layer message to the network device and waiting for an RRC connection reconfiguration message sent by the network device, so that the problems that the interruption time of the uplink data transmission of the DRB is long and the time delay is generated due to the fact that the DRB sends the radio resource control layer message and waits for the RRC connection reconfiguration message are avoided.

In one possible design, the first network device refers to a primary base station in a dual-connectivity communication system, and the second network device refers to a secondary base station in the dual-connectivity communication system.

In one possible design, the first bearer type is a Split bearer and the second bearer type is an MCG bearer.

In one possible design, the converting the type of the DRB from the first bearer type to the second bearer type is performed before the terminal receives an RRC connection reconfiguration message sent by the first network device to convert the type of the DRB from the first bearer type to the second bearer type. By the data transmission method, in the process of data transmission of dual connectivity, if the terminal performs uplink data transmission on the DRB configured as Split bearer, when the terminal detects that the cell group under the secondary base station is unavailable, the type of the DRB is converted from the Split bearer to the MCG bearer, and then the path for performing the uplink data transmission on the DRB is converted into the path only through the MCG transmission, so that the problem of long uplink data transmission interruption time of the DRB caused by transmitting a radio resource control layer message, waiting for an RRC connection reconfiguration message and converting the type of the DRB from the Split bearer to the MCG bearer when the cell group under the secondary base station is detected to be unavailable is solved, and the uplink data transmission delay of the DRB is reduced.

In one possible design, before the DRB type is converted from the first bearer type to the second bearer type, the terminal needs to determine that the path for the uplink data transmission on the DRB includes a path for transmission through the second cell group, so as to avoid the waste of terminal resources caused by switching the DRB type when the path for the uplink data transmission on the DRB is only transmitted through the first cell group.

In one possible design, the determining, by the terminal, that the path for the uplink data transmission on the DRB includes a path for transmission through the second cell group includes: determining that a first uplink data amount transmitted on the DRB is greater than or equal to a threshold value; or, determining that the first uplink data amount transmitted on the DRB is smaller than the threshold, and the RLC entity corresponding to the first cell group is the secondary RLC entity corresponding to the first bearer type, and the RLC entity corresponding to the second cell group is the primary RLC entity corresponding to the first bearer type.

In one possible design, the first uplink data amount at the DRB includes: a first data volume transmitted through the PDCP entity of the DRB, a first data volume waiting for initial transmission in the RLC entity corresponding to the first cell group, and a first data volume waiting for initial transmission in the RLC entity corresponding to the second cell group.

In one possible design, the condition that the terminal determines that the second set of cells accessed is unavailable is at least one of: the quality of at least one cell in the cell or the group of cells under the second network device is lower than a certain threshold value, an A2 event is met, and a measurement report is triggered; the T310 timer for monitoring the radio link failure corresponding to the primary cell under the second network device is overtime; a random access event occurs in a primary cell under the second network device; the data retransmission times of at least one RLC entity in the RLC entities corresponding to the second cell group reach the maximum transmission times; the RRC configuration of the second cell group fails; the PDCP entity of at least one of the DRBs receives an indication of a failure of an integrity check of a PDCP Protocol Data Unit (PDU) or a PDCP Service Data Unit (SDU) from the RLC entity corresponding to the second cell group.

In one possible design, after determining that the accessed second cell group is not available, the method further includes: sending a Buffer Status Report (BSR) containing a second uplink data volume transmitted on the DRB to the first network device, wherein the second uplink data volume transmitted on the DRB comprises a second data volume transmitted by a PDCP entity of the DRB and a second data volume corresponding to an RLC entity of the first cell group. Through the possible design, the first network device can conveniently acquire the uplink data amount of the terminal which still needs to perform uplink data transmission through the DRB after the terminal is unavailable in the second cell group, and perform uplink scheduling authorization for the terminal.

In one possible design, after the terminal converts the type of the DRB from the first bearer type to the second bearer type, the terminal performs a data recovery procedure of the PDCP entity of the DRB or performs a re-establishment procedure of the PDCP entity of the DRB. Through the design, the integrity and the accuracy of uplink data transmission can be ensured.

In a second aspect, there is provided a data transmission apparatus having the functionality of implementing the method of the first aspect and any one of the possible designs. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In one possible design, the device may be a chip or an integrated circuit.

In one possible design, the apparatus includes a transceiver and a processor for executing a set of programs, and when the programs are executed, the apparatus may perform the method of the first aspect and any one of the possible designs.

In one possible design, the apparatus further includes a memory for storing a program executed by the processor.

In one possible design, the device is a terminal.

In a third aspect, a computer storage medium is provided that stores a computer program comprising instructions for performing the method in any of the possible designs of the above aspects and aspects.

In a fourth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method as described in the aspects and any possible design of aspects.

In a fifth aspect, a chip is provided, which is connected to a memory for reading and executing a software program stored in the memory to implement the method in any one of the possible designs of the above aspects and aspects.

The beneficial effect of this application is as follows: if the DRB for the terminal to perform uplink data transmission is a first bearer type of a PDCP entity configured to associate an RLC entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, wherein the first cell group belongs to a first network device, and the second cell group belongs to a second network device; when the terminal determines that the accessed second cell group is unavailable, the type of the DRB is converted from the first bearer type to a second bearer type of a PDCP entity which is only associated with an RLC entity corresponding to the first cell group, so that the problem that the time for uplink data transmission interruption of the DRB is long due to the fact that the terminal waits for an RRC connection reconfiguration message sent by first network equipment after determining that the accessed second cell group is unavailable and then converts the type of the DRB from the first bearer type to the second bearer type is solved, and the uplink data transmission delay of the DRB is reduced.

Drawings

FIG. 1a is a schematic diagram of a dual connectivity communication system according to an embodiment of the present application;

FIG. 1b is a second schematic diagram of the architecture of the dual connectivity communication system in the embodiment of the present application;

fig. 2 is a schematic diagram of bearer types perceived by a terminal side in an embodiment of the present application;

fig. 3 is a schematic view of a bearer type perceived by a base station side in an embodiment of the present application;

fig. 4 is one of the schematic diagrams of the Split bearer terminated by MN in the embodiment of the present application;

fig. 5 is one of the schematic diagrams of SN terminated Split bearers in the embodiment of the present application;

fig. 6 is a schematic signaling flow diagram illustrating a control of data transmission by a terminal according to an embodiment of the present application;

fig. 7 is a second schematic signaling flow chart illustrating the control of data transmission by the terminal according to the embodiment of the present application;

fig. 8 is a second schematic diagram of MN terminated Split bearers in the present embodiment;

FIG. 9 is a second example of SN terminated Split bearer in the present application;

fig. 10 is a third schematic signaling flow chart illustrating control of data transmission by the terminal according to the embodiment of the present application;

fig. 11 is a fourth schematic signaling flow diagram illustrating a terminal controlling data transmission according to an embodiment of the present application;

fig. 12 is a schematic flow chart of a data transmission method in an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present application;

fig. 14 is a second schematic structural diagram of a data transmission device in the embodiment of the present application.

Detailed Description

The application provides a data transmission method and device, which are used for reducing the uplink data transmission delay of a DRB (dual connectivity broadband wireless access) when a terminal configured with dual connectivity performs the data transmission on the DRB. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

Some terms of the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

1) A terminal, also referred to as User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user. For example, the terminal device includes a handheld device, an in-vehicle device, and the like having a wireless connection function. Currently, the terminal device may be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (smart security), a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like.

2) The base stations may also be referred to as Radio Access Network (RAN) nodes/devices, and in a dual-connection networking mode, a terminal is simultaneously connected to two base stations, where one base station is a master base station and the other is a slave base station, and in this application, the master base station/node may also be referred to as a first network device and the slave base station/node may also be referred to as a second network device.

3) The cell group (cell group) is configured for a terminal and belongs to a main base station and a secondary base station respectively, and is divided into two groups, wherein the cell group belonging to the main base station is named as MCG, the cell group belonging to the secondary base station is named as SCG, the MCG can also be named as a first cell group in the application, and the SCG can also be named as a second cell group.

4) MCG bearer (MCG bearer), SCG bearer (MCG bearer), and Split bearer (Split bearer/Split bearer), where MCG bearer is a radio bearer in which RLC bearer is configured only in MCG; the SCG bearer is a radio bearer of which the RLC bearer is only configured in the SCG; the Split bearer is a radio bearer in which an RLC bearer is configured in both an MCG and an SCG, wherein the RLC bearer refers to an RLC configuration and a logical channel configuration of one radio bearer in one cell group. Split bearers may also be referred to as a first bearer type and MCG bearers may also be referred to as a second bearer type in this application.

5) A bearer terminated by a Master Node (MN) and a bearer terminated by a Secondary Node (SN), where the bearer terminated by the MN is also referred to as a bearer terminated by a master base station and refers to a radio bearer of the PDCP at the master base station/node; SN terminated bearers, also referred to as secondary base station terminated bearers, refer to the radio bearers of the PDCP at the secondary base station/node.

6) "and/or" describe the association relationship of the associated objects, indicating that there may be three relationships, e.g., a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

The plural in the present application means two or more.

In addition, it is to be understood that the terms first, second, etc. in the description of the present application are used for distinguishing between the descriptions and not necessarily for describing a sequential or chronological order.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 1a is a structure of a dual connectivity communication system to which the data transmission method provided in the embodiment of the present invention is applicable, as shown in fig. 1a, a terminal may access a network device 1 of a first communication system and a network device 2 of a second communication system, and a connection exists between the network device 1 and the network device 2, where the first communication system and the second communication system may be the same or different, for example, the first communication system and the second communication system may both be 5G, or the first communication system may be 4G, and the second communication system is 5G. As shown in fig. 1b, for a dual connectivity communication system architecture in an EN-DC networking manner, a terminal accesses to 4G and 5G network devices simultaneously, specifically, the dual connectivity communication system includes: the terminal is connected to the LTE base station and the NR base station simultaneously, wherein the eNB is MeNB, and the En-gNB is SgNB; the eNB is respectively connected to the MME of the 4G core network and the S-GW through a control plane (S1-C) interface and a user plane (S1-U) interface, the En-gNB is not connected with the MME of the 4G core network, and whether the connection with the S-GW of the 4G core network is achieved through the S1-U interface is determined according to the protocol stack architecture of the EN-DC; the eNB and the En-gNB are connected through an interconnection interface (X2).

It should be understood that the embodiment of the present application may also be applied to a dual connectivity communication system of a networking system, such as an EN-DC networking system shown in fig. 1b, an NE-DC networking system, an NGEN-DC networking system, or an NR-NR DC networking system. In a NE-DC networking mode dual-connection communication system, a terminal is simultaneously connected to a 5G NR base station and a 4G LTE base station, the NR base station is a main base station/node and is also called as MgNB in NE-DC; eNB is a secondary base station/node, also known as SeNB in NE-DC; in a dual-connection system of an NGEN-DC networking mode, a terminal is simultaneously connected to a 4G LTE base station and a 5G NR base station, wherein the NR base station is a main base station/node and is also called as an MeNB in the NGEN-DC; the LTE base station is an auxiliary base station/node and is also called as SgNB in NGEN-DC; in a double-connection system of an NR-NR DC networking mode, a terminal is simultaneously connected to two 5G NR base stations, and one NR base station is a main base station/node, namely MgNB; another NR base station is a secondary base station/node, SgNB.

In the dual-connection communication system, from the perspective of the terminal, the terminal can sense three types of bearers, namely MCG bearer, SCG bearer and Split bearer, according to whether the RLC entity of the terminal corresponds to the RLC entity of the MCG and/or SCG; from the perspective of the base station, according to whether the RLC bearer is an RLC entity configured in the MCG and/or SCG, and whether the PDCP is located in the MeNB or the SgNB, the base station can sense six bearers, that is, an MN-terminated MCG bearer, an MN-terminated SCG bearer, an MN-terminated Split bearer, an SN-terminated MCG bearer, an SN-terminated SCG bearer, and an SN-terminated Split bearer.

Now, a dual-connectivity communication system based on the EN-DC networking method will be specifically described, where: as shown in fig. 2, if the RLC entity of the terminal is the LTE RLC entity corresponding to the MCG, it is determined that the terminal side is MCG bearer; if the RLC entity of the terminal is the NR RLC entity corresponding to the SCG, determining that the terminal side is loaded by the SCG; and if the RLC entities of the terminal are the LTE RLC entity corresponding to the MCG and the NR RLC entity corresponding to the SCG, determining that the terminal side is the Split bearer.

For the base station side, as shown in fig. 3, under the condition that the PDCP is located in the MeNB, that is, the PDCP is located in the LTE base station, if the RLC entity of the base station is the LTE RLC entity configured in the MCG, it is determined that the base station side is an MCG bearer terminated by the MN; if the RLC entity of the base station is the NR RLC entity configured in the SCG, determining that the base station side is the SCG bearing terminated by the MN; and if the RLC entities of the base station are the LTE RLC entity configured in the MCG and the NR RLC entity configured in the SCG, determining that the base station side is the Split bearer terminated by the MN. When the PDCP is located in the SgNB, namely the PDCP is located in the NR base station, if the RLC entity of the base station is the LTE RLC entity configured in the MCG, the base station side is determined to be the MCG bearing terminated by the SN; if the RLC entity of the base station is an NR RLC entity configured in the SCG, determining that the base station side is SCG bearing terminated by SN; and if the RLC entities of the base station are the LTE RLC entity configured in the MCG and the NR RLC entity configured in the SCG, determining that the base station side is the Split bearer terminated by the SN.

When a DRB for uplink data transmission by a terminal is configured as a Split bearer, the terminal can determine a path for uplink data transmission by the terminal on the DRB according to a cell group corresponding to an RLC entity of the DRB configured as the Split bearer, that is, a cell group corresponding to an RLC entity associated with a PDCP entity of the DRB configured as the Split bearer, and a threshold value of an uplink data volume that the terminal configured by a network device can simultaneously transmit through an MCG and an SCG, where the network device configured with the threshold value may be a primary base station and/or a secondary base station.

Specifically, if the first uplink data volume of the DRB is greater than or equal to the threshold value, it is determined that the path through which the terminal performs uplink data transmission on the DRB is simultaneously transmitted through the MCG and the SCG; if the first uplink data volume of the DRB is smaller than the threshold, and the primary RLC entity of the DRB configured as Split bearer is an RLC entity corresponding to an MCG, the secondary RLC entity is an RLC entity corresponding to an SCG, or the RLC bearer corresponding to the primary path associated with the PDCP entity of the DRB configured as Split bearer is an RLC bearer corresponding to an MCG, and the RLC bearer corresponding to the secondary path is an RLC bearer corresponding to an SCG, determining that a path through which the terminal performs uplink data transmission on the DRB is MCG transmission; if the first uplink data volume of the DRB is smaller than the threshold, and the primary RLC entity of the DRB configured as Split bearer is an RLC entity corresponding to SCG, the secondary RLC entity is an RLC entity corresponding to MCG, or the RLC bearer corresponding to the primary path associated with the PDCP entity of the DRB configured as Split bearer is an RLC bearer corresponding to SCG, and the RLC bearer corresponding to the secondary path is an RLC bearer corresponding to MCG, determining that a path through which the terminal performs uplink data transmission on the DRB is SCG transmission.

Wherein the first uplink data volume of the DRB includes:

a first data volume transmitted through the PDCP entity of the DRB, a first data volume waiting for initial transmission in the RLC entity corresponding to the first cell group, and a first data volume waiting for initial transmission in the RLC entity corresponding to the second cell group.

Because if the path through which the terminal performs uplink data transmission on the DRB is MCG transmission, the terminal does not interrupt the uplink data transmission on the DRB because the SCG is unavailable, in order to simplify the control process of data transmission, in this application, the terminal may only use the path through which the terminal performs uplink data transmission on the DRB as a scenario in which the path through which the terminal performs uplink data transmission on the DRB is SCG transmission and the path through which the terminal performs uplink data transmission on the DRB is MCG and SCG transmission at the same time, and when it is determined that the accessed SCG is unavailable, the DRB is converted from Split bearer to MCG bearer, so that the path through which the terminal performs uplink data transmission on the DRB is converted into MCG transmission only. Specifically, the terminal converts the DRB from a Split bearer to an MCG bearer, and before the terminal receives the RRC connection reconfiguration message sent by the MeNB.

Wherein the condition that the terminal determines that the accessed SCG is unavailable is at least one of the following conditions: (1) the measurement result of the terminal in at least one cell in the cell or the cell group under the secondary base station meets an A2 event, namely the quality of at least one cell in the cell or the cell group under the secondary base station is lower than a certain threshold value, and the terminal triggers the sending of a measurement report to the main base station; (2) the timer T310 for monitoring the radio link failure corresponding to the main cell of the terminal under the auxiliary base station is overtime; (3) the terminal generates a random access event in a main cell under the auxiliary base station; (4) the terminal corresponding to at least one RLC entity in the SCG RLC entities has the maximum transmission times; (5) the RRC configuration of the SCG of the terminal fails; (6) the PDCP entity of at least one of the DRBs receives an indication of a PDCP PDU or PDCP SDU integrity check failure from the RLC entity corresponding to the SCG.

Hereinafter, EN-DC will be described as an example, with reference to a specific scenario.

Scene one: the terminal performs uplink data transmission on the DRB configured as a Split bearer through the SCG, and when determining that the accessed SCG is unavailable, the terminal converts the DRB from the Split bearer into an MCG bearer.

Specifically, the Split bearer includes, for the base station side, a MN terminated Split bearer as shown in fig. 4 and an SN terminated Split bearer as shown in fig. 5.

For the scenario one, in a signaling flow in which a terminal in the prior art controls data transmission, as shown in fig. 6, a DRB of the terminal is configured as a Split bearer, and a path on which uplink data transmission is performed on the DRB is through SCG transmission; the terminal transmits the uplink data of the DRB through the SCG; when the terminal detects that the SCG is unavailable, a Scheduling Request (SR) is triggered to request uplink resources from the MeNB for sending a radio resource control layer message, wherein the radio resource control layer message comprises: SCG failure (failure) information or a measurement report is sent after uplink scheduling authorization of the MeNB is obtained; after receiving an RRC connection reconfiguration (reconfiguration) message sent by the MeNB, if the RRC connection reconfiguration message indicates that the terminal converts the DRB from a Split bearer to an MCG bearer, an RRC layer of the terminal configures a PDCP entity of the DRB to only associate with its LTE RLC entity, transforms the Split bearer of the DRB into an MCG bearer, sends an RRC reconfiguration complete message to the MeNB, and controls the PDCP entity of the DRB to start a data recovery (data recovery) process of the PDCP entity of the DRB or perform a reconstruction process of the PDCP entity of the DRB, and sends an SR/BSR to the MeNB to request an uplink resource for transmitting an uplink data volume still required to be sent by the DRB, and after obtaining an uplink scheduling authorization of the MeNB, transmits the uplink data still required to be sent by the DRB through the MCG.

Fig. 7 is a signaling flow of the present application for controlling data transmission by a terminal in a scenario one, where a DRB of the terminal is configured as a Split bearer, and a path for performing uplink data transmission on the DRB is transmission through an SCG; the terminal transmits the uplink data of the DRB through the SCG; when the terminal detects that the SCG is unavailable, the RRC layer of the terminal configures the PDCP entity of the DRB to only associate with the LTE RLC entity of the terminal, converts the Split bearer of the DRB into an MCG bearer, and controls the PDCP entity of the DRB to start executing a Data recovery process of the PDCP entity of the DRB or execute a reconstruction process of the PDCP entity of the DRB; and triggering the SR to request uplink resources from the MeNB for sending the SCG failure message or the measurement report, after obtaining the uplink resource scheduling authorization of the MeNB, sending the SCG failure message or the measurement report and the BSR containing the second uplink data volume of the DRB, after obtaining the uplink scheduling authorization of the MeNB for the second uplink data volume of the DRB, transmitting the uplink data still required to be sent by the DRB through the MCG, and receiving the RRC reconfiguration message sent by the MeNB to complete the processing.

The following still takes a dual-connection system in an EN-DC networking mode, that is, an LTE base station is MeNB, and an NR base station is SgNB as an example, to describe a specific processing procedure in the terminal:

firstly, RRC layer processing of a terminal:

1. when an RRC layer of a terminal determines that SCG in dual connectivity is unavailable, namely when a cell group of an NR base station is unavailable, if a DRB for uplink data transmission of the terminal is configured as a Split bearer, a main RLC entity associated with the PDCP entity of the DRB is an RLC entity corresponding to the SCG, and a first uplink data volume of the DRB is smaller than a threshold value configured by network equipment, the RRC layer of the terminal sends an indication (indication) to the PDCP entity of the DRB. The indication is used to notify the PDCP entity to perform corresponding processing according to the indication, and specifically, the indication may be configured such that the PDCP entity of the DRB is only associated with the RLC entity of the corresponding MCG after the terminal detects that the SCG is unavailable and before receiving an RRC connection reconfiguration message sent by the LTE base station.

The specific information of the Indication includes:

for a DRB configured in Unacknowledged (UM) mode and carried by Split terminated by MN, the indication indicates that the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only maintains association with the RLC entity of the MCG.

For a DRB configured in Acknowledged (AM) mode and carried by Split terminated by MN, the indication indicates that the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only maintains association with the RLC entity of the MCG.

Further, the indication may also instruct the PDCP entity of the DRB to start performing a PDCP Data recovery procedure or start performing a retransmission procedure of an uplink PDCP PDU in the PDCP Data recovery procedure;

for a DRB configured as an AM mode and terminated by SN, the indication indicates that the PDCP entity of the DRB only maintains an association with the LTE RLC entity, but not the NR RLC entity, i.e. only maintains an association with the RLC entity of the MCG.

In addition, for the DRB configured as a Split bearer terminated by SN, the RRC layer of the terminal changes the used security algorithm from the algorithm configured by SgNB to the algorithm configured by MeNB, and changes the security key from S-KgNB corresponding to SgNB to KeNB corresponding to MeNB. And then informing the PDCP layer of the terminal of the algorithm and the key used after modification.

Secondly, PDCP layer processing of the terminal:

specifically, the PDCP layer of the terminal performs processing after the DRB entity receives the indication sent by the RRC layer.

1. The delivery of the PDCP PDUs to the corresponding NR RLC entities is stopped.

2. For DRBs configured as MN terminated Split bearers, the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only with the RLC entity of the MCG. Further, if the DRB is in UM mode, the PDCP entity starts to deliver PDCP PDUs to the LTE RLC, i.e. without waiting for receiving the request of the LTE RLC, the PDCP PDUs are delivered to the LTE RLC; if there are PDCP PDUs that have not started transmission at the NR RLC, the PDCP entity retransmits the PDCP PDUs through the LTE RLC. Therefore, packet loss of the UM mode Split bearer is reduced as much as possible; further, if the DRB is in the AM mode, the PDCP entity starts to perform uplink Data retransmission in the PDCP Data recovery procedure, that is, the PDCP PDUs which have been delivered to the NR RLC entity but have not been successfully transmitted are delivered to the LTE RLC entity again for retransmission, or the PDCP Data recovery procedure is started.

3. For DRBs configured as SN terminated Split bearers, the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only with the RLC entity of the MCG. Further, the PDCP entity starts performing a PDCP re-establishment procedure;

4. and indicating the second uplink data volume of the DRB to the LTE MAC. Specifically, the second uplink data amount of the DRB includes a second data amount transmitted by the PDCP entity and a second data amount in an LTE RLC entity associated with the PDCP entity.

Thirdly, processing of the MAC layer of the terminal:

1. the MAC layer triggers a BSR and sends a measurement report or an SCG failure message.

2. When the terminal receives an uplink scheduling grant (UL grant), the logical channel corresponding to the DRB already has data to be transmitted, i.e. both the PDCP entity and the LTE RLC entity of the DRB already have data to be transmitted. Therefore, in the BSR transmitted simultaneously with the measurement report or the SCG failure message, the MAC may report the second uplink data amount of the DRB. Further, if the UL grant can accommodate the MAC PDU carried by the Split in addition to the measurement report or the SCG failure message and the BSR, the terminal can also transmit the MAC SDU carried by the Split through the UL grant.

Scene two: the terminal transmits the uplink data on the DRB configured as the Split bearer through the MCG and the SCG at the same time, and when determining that the accessed SCG is unavailable, the terminal converts the DRB from the Split bearer into the MCG bearer.

Specifically, the Split bearer includes, for the base station side, a MN terminated Split bearer as shown in fig. 8 and an SN terminated Split bearer as shown in fig. 9.

For the scenario two, in the signaling flow for controlling data transmission by the terminal in the prior art, as shown in fig. 10, a DRB of the terminal is configured as a Split bearer, and a path for performing uplink data transmission on the DRB is simultaneously transmitted through an MCG and an SCG; the terminal transmits the uplink data of the DRB through the MCG and the SCG simultaneously; when the terminal detects that SCG is unavailable, the terminal triggers the SR to request uplink resources from the MeNB for sending an SCG failure message or a measurement report, after the uplink scheduling authorization of the MeNB is obtained, the SCG failure message or the measurement report and the BSR are sent, after the terminal receives the uplink scheduling authorization and the RRC reconfiguration message sent by the MeNB, if the RRC connection reconfiguration message indicates that the terminal converts the DRB from a Split bearer to an MCG bearer, the RRC layer of the terminal configures the PDCP entity of the DRB only to be associated with the LTE RLC entity of the DRB, converts the Split bearer of the DRB into the MCG bearer, sends an RRC reconfiguration completion message to the MeNB, controls the PDCP entity of the DRB to start to execute a Data recovery process of the PDCP entity of the DRB or execute a reconstruction process of the PDCP entity of the DRB, and transmits the PDCP PDU or the SDU through the SCG before the terminal transmits through the MCG.

Fig. 11 is a signaling flow of the present application for controlling data transmission by a terminal in the second scenario, where a DRB of the terminal is configured as a Split bearer, and a path for performing uplink data transmission on the DRB is simultaneously transmitted through an MCG and an SCG; the terminal transmits the uplink data of the DRB through the MCG and the SCG simultaneously; when the terminal detects that the SCG is unavailable, the RRC layer of the terminal configures the PDCP entity of the DRB to only associate with the LTE RLC entity of the terminal, converts the Split bearer of the DRB into an MCG bearer, and controls the PDCP entity of the DRB to start executing a Data recovery process of the PDCP entity of the DRB or execute a reconstruction process of the PDCP entity of the DRB; the terminal triggers the SR to request uplink resources to send SCG failure messages or measurement reports to the MeNB, after uplink scheduling authorization of the MeNB is obtained, the SCG failure messages or measurement reports and the BSR are sent, the terminal receives the uplink scheduling authorization sent by the MeNB, and after PDCP PDU or PDCP SDU transmitted by the SCG before MCG transmission is received, the RRC reconfiguration message sent by the MeNB is received, and the processing is completed.

The following still takes a dual-connection system in an EN-DC networking mode, that is, an LTE base station is an MeNB, and an NR base station is an auxiliary base station as an example, to describe a specific processing procedure in a terminal:

firstly, RRC layer processing of a terminal:

1. when the RRC layer of the terminal determines that SCG in dual connectivity is unavailable, namely when a cell group of an NR base station is unavailable, if a DRB for uplink data transmission of the terminal is configured as a Split bearer and the first uplink data volume of the DRB is greater than or equal to a threshold value configured by network equipment, the RRC layer of the terminal sends an indication to a PDCP entity of the DRB. The indication is used to notify the PDCP entity to perform corresponding processing according to the indication, and specifically, the indication may be configured such that the PDCP entity of the DRB is only associated with the RLC entity of the corresponding MCG after the terminal detects that the SCG is unavailable and before receiving an RRC connection reconfiguration message sent by the LTE base station.

The specific information of the Indication includes:

for DRBs configured in UM mode and carried by Split terminated by MN, the indication indicates that the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only maintains association with the RLC entity of the MCG.

For a DRB configured in AM mode and carried by Split terminated by MN, the indication indicates that the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only maintains association with the RLC entity of the MCG.

Secondly, processing a PDCP layer of the terminal:

1. The delivery of the PDCP PDUs to the NR RLC entity is stopped.

2. For DRBs configured as MN terminated Split bearers, the PDCP entity of the DRB only maintains association with the LTE RLC entity and no longer with the NR RLC entity, i.e. only with the RLC entity of the MCG. Further, if the DRB is in UM mode and is transmitted through both MCG and SCG paths, the PDCP entity delivers PDCP PDUs to the NR RLC without receiving a NR RLC request, and if there are PDCP PDUs which have not started transmission at the NR RLC, the PDCP entity retransmits the PDCP PDUs through the LTE RLC. Further, if the DRB is in the AM mode, the PDCP entity starts to perform an uplink Data retransmission process in the PDCP Data recovery process, that is, the PDCP PDUs which have been delivered to the NR RLC entity but have not been successfully transmitted are delivered to the LTE RLC entity again for retransmission, or the PDCP Data recovery process is started.

3. For a DRB configured as a SN-terminated Split bearer, the PDCP entity of the DRB only maintains association with an LTE RLC entity and no longer with an NR RLC entity, namely only maintains association with an RLC entity of an MCG, and further, the PDCP entity starts to perform a PDCP re-establishment process;

4. and indicating the second uplink data volume of the DRB to an LTE MAC. Wherein the second uplink data amount of the DRB comprises a second data amount transmitted by the PDCP entity and a second data amount in an LTE RLC entity associated with the PDCP entity.

More specifically, the second uplink data amount of the DRB includes a data amount corresponding to a PDCP PDU that needs to be retransmitted or a PDCP SDU that needs to be retransmitted in the PDCP entity of the DRB, and a data amount of the PDCP entity of the DRB excluding the data amount corresponding to the PDCP PDU that needs to be retransmitted or the data amount corresponding to the PDCP SDU that needs to be retransmitted and a data amount of an LTE entity associated with the PDCP entity.

Processing of the MAC layer of the terminal:

2. When the terminal receives the UL grant, the MAC may report the second uplink data amount of the DRB in the BSR transmitted simultaneously with the measurement report or the SCG failure message.

By the embodiment, when the SCG cell is not available, the time delay of DRB which is configured to be carried by Split by the terminal and is caused by the fact that the receiving end needs to reorder the PDCP PDUs due to delayed retransmission of part of the PDCP PDUs can be reduced.

Based on the foregoing embodiments, as shown in fig. 12, an embodiment of the present application provides a communication method, which includes the specific steps of:

s1201: the terminal carries out uplink data transmission on a DRB, wherein the DRB is a first bearer type, a PDCP entity of the first bearer type is configured to associate an RLC entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, the first cell group belongs to a first network device, and the second cell group belongs to a second network device.

S1202: and when the terminal determines that the accessed second cell group is unavailable, the type of the DRB is converted from the first bearer type to a second bearer type, and the PDCP entity of the second bearer type is only associated with the RLC entity corresponding to the first cell group.

Preferably, after the type of the DRB is converted from the first bearer type to the second bearer type, the terminal performs a data recovery procedure of the PDCP entity of the DRB, or performs a reestablishment procedure of the PDCP entity of the DRB; and sending the generated radio resource control layer message and the triggered BSR containing the second uplink data volume of the DRB to the first network equipment.

Wherein the second uplink data volume of the DRB comprises a second data volume transmitted by the PDCP entity of the DRB and a second data volume in the RLC entity corresponding to the first cell group.

Based on the same inventive concept as the above-described communication method, as shown in fig. 13, an embodiment of the present invention further provides a data transmission apparatus 1300, where the data transmission apparatus 1300 is configured to perform an operation performed by a terminal in the above-described communication method, and the communication apparatus 1300 includes: processing section 1301 and transmitting/receiving section 1302. The transceiving unit 1302, configured to perform uplink data transmission on a DRB, where the DRB is a first bearer type, and a PDCP entity of the first bearer type is configured to associate an RLC entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, where the first cell group belongs to a first network device and the second cell group belongs to a second network device; a processing unit 1301, configured to convert the type of the DRB from the first bearer type to a second bearer type when it is determined that the accessed second cell group is unavailable, where a PDCP entity of the second bearer type is only associated with an RLC entity corresponding to the first cell group.

Based on the same inventive concept as the above communication method, as shown in fig. 14, an embodiment of the present application further provides a communication apparatus 1400, where the communication apparatus 1400 is configured to perform an operation performed by a terminal in the above communication method, and the communication apparatus 1400 includes: the processor 1401 and the transceiver 1402, and optionally, the memory 1403. The process 1401 is for calling a set of programs, which when executed, cause the processor 1401 to execute the operations performed by the terminal in the above-described communication method. The memory 1403 is used for storing programs executed by the processor 1401. The functional module processing units 1301 in fig. 13 may be implemented by the processor 1401, and the transceiving unit 1302 may be implemented by the transceiver 1402.

Processor 1401 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.

Processor 1401 may further include a hardware chip or other general purpose processor. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The aforementioned PLDs may be Complex Programmable Logic Devices (CPLDs), field-programmable gate arrays (FPGAs), General Array Logic (GAL) and other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., or any combination thereof. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory 1403 referred to in the embodiments of the application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), 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), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, synchronous link SDRAM, and direct rambus DRAM. It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application provides a computer storage medium, which stores a computer program, wherein the computer program comprises a program for executing the data transmission method.

Embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the data transmission method provided above.

Any kind of data transmission device that this application embodiment provided can also be a chip.

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 embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A method of data transmission, comprising:

a terminal carries out uplink data transmission on a Data Radio Bearer (DRB), wherein the DRB is a first bearer type, a Packet Data Convergence Protocol (PDCP) entity of the first bearer type is configured to associate a radio link control protocol (RLC) entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, the first cell group belongs to a first network device, and the second cell group belongs to a second network device;

when the terminal determines that the accessed second cell group is unavailable, the type of the DRB is converted from the first bearer type to a second bearer type, and the PDCP entity of the second bearer type is only associated with the RLC entity corresponding to the first cell group;

wherein the first bearer type is a Split bearer, and the second bearer type is an MCG bearer; after converting the type of the DRB from the first bearer type to a second bearer type, the method further includes:

the terminal receives a radio resource control layer RRC connection reconfiguration message which is sent by the first network equipment and used for converting the type of the DRB from the first bearer type to a second bearer type;

before converting the type of the DRB from the first bearer type to a second bearer type, the method further includes:

the terminal determines that a path for the uplink data transmission on the DRB includes a path for transmission through the second cell group.

2. The method of claim 1, wherein the terminal determining that the path for the uplink data transmission on the DRB comprises a path for transmission through the second cell group comprises:

determining that a first uplink data amount transmitted on the DRB is greater than or equal to a threshold value; alternatively, the first and second electrodes may be,

and determining that the first uplink data volume transmitted on the DRB is smaller than the threshold value, and the RLC entity corresponding to the first cell group is the auxiliary RLC entity corresponding to the first bearer type, and the RLC entity corresponding to the second cell group is the main RLC entity corresponding to the first bearer type.

3. The method of claim 2, wherein the first amount of uplink data transmitted on the DRB comprises:

4. The method of any of claims 1-3, wherein the terminal determines that the second group of cells accessed is unavailable when at least one of the following conditions is met:

the quality of at least one cell in the cell or the group of cells under the second network device is lower than a certain threshold value, an A2 event is met, and a measurement report is triggered;

the T310 timer for monitoring the radio link failure corresponding to the primary cell under the second network device is overtime;

a random access event occurs in a primary cell under the second network device;

the data retransmission times of at least one RLC entity in the RLC entities corresponding to the second cell group reach the maximum transmission times;

the RRC configuration of the second cell group fails;

the PDCP entity of at least one of the DRBs receives an indication of a PDCP protocol data unit PDU or a PDCP service data unit SDU integrity check failure from the RLC entity corresponding to the second cell group.

5. The method of any of claims 1-3, wherein after converting the type of the DRB from the first bearer type to a second bearer type, further comprising:

and the terminal executes the data recovery process of the PDCP entity of the DRB or executes the reconstruction process of the PDCP entity of the DRB.

6. The method of any of claims 1-3, wherein after determining that the accessed second cell group is unavailable, the method further comprises:

and sending a Buffer Status Report (BSR) containing a second uplink data volume transmitted on the DRB to the first network equipment, wherein the second uplink data volume transmitted on the DRB comprises the second data volume transmitted by the PDCP entity of the DRB and a second data volume in the RLC entity corresponding to the first cell group.

7. A data transmission device is characterized by comprising a transceiving unit and a processing unit;

the transceiver unit is configured to perform uplink data transmission on a data radio bearer DRB, where the DRB is a first bearer type, and a packet data convergence protocol PDCP entity of the first bearer type is configured to associate a radio link control protocol RLC entity corresponding to a first cell group and an RLC entity corresponding to a second cell group, where the first cell group belongs to a first network device and the second cell group belongs to a second network device;

the processing unit is configured to convert the type of the DRB from the first bearer type to a second bearer type when determining that the accessed second cell group is unavailable, where a PDCP entity of the second bearer type is only associated with an RLC entity corresponding to the first cell group;

wherein the first bearer type is a Split bearer, and the second bearer type is an MCG bearer; the transceiver unit is further configured to receive a radio resource control layer RRC connection reconfiguration message sent by the first network device to convert the type of the DRB from the first bearer type to a second bearer type after the processing unit converts the type of the DRB from the first bearer type to the second bearer type;

the processing unit is further configured to determine, before the type of the DRB is converted from the first bearer type to a second bearer type, that a path on which the uplink data transmission is performed on the DRB includes a path transmitted through the second cell group.

8. The apparatus of claim 7, wherein the processing unit is specifically configured to determine that the first amount of uplink data transmitted on the DRB is greater than or equal to a threshold value; or, when it is determined that the first uplink data amount transmitted on the DRB is smaller than the threshold, and the RLC entity corresponding to the first cell group is the secondary RLC entity corresponding to the first bearer type, and the RLC entity corresponding to the second cell group is the primary RLC entity corresponding to the first bearer type, determining that the path for transmitting the uplink data on the DRB includes a path for transmitting through the second cell group.

9. The apparatus of claim 8, wherein the first amount of uplink data transmitted on the DRB comprises:

10. The apparatus of any one of claims 7-9, wherein the processing unit determines that the second group of cells accessed is unavailable when at least one of the following conditions is met:

a random access event occurs in a primary cell under the second network device;

the RRC configuration of the second cell group fails;

11. The apparatus of any one of claims 7-9, wherein the processing unit is further configured to perform a data recovery procedure for the PDCP entity of the DRB or perform a re-establishment procedure for the PDCP entity of the DRB after the type of the DRB is converted from the first bearer type to the second bearer type.

12. The apparatus of any of claims 7-9, wherein the transceiver unit is further configured to send a Buffer Status Report (BSR) to the first network device containing a second amount of uplink data transmitted on the DRB after the processing unit determines that the accessed second cell group is not available, wherein the second amount of uplink data transmitted on the DRB comprises the second amount of data transmitted by the PDCP entity of the DRB and the second amount of data in the RLC entity corresponding to the first cell group.

13. A terminal comprising a memory, a transceiver, and a processor;

the memory stores a computer program;

the transceiver is used for transmitting and receiving data;

the processor, for invoking a computer program stored in the memory, to execute the method of any of claims 1-6 via the transceiver.

14. A computer storage medium having computer readable instructions stored thereon which, when read and executed by a computer, cause the computer to perform the method of any one of claims 1 to 6.

15. A chip, characterized in that it is connected to a memory for reading and executing a software program stored in said memory for implementing the method according to any one of claims 1 to 6.