CN113507725A - Data transmission method and device in separated bearer mode and terminal equipment - Google Patents

Data transmission method and device in separated bearer mode and terminal equipment Download PDF

Info

Publication number
CN113507725A
CN113507725A CN202110795254.7A CN202110795254A CN113507725A CN 113507725 A CN113507725 A CN 113507725A CN 202110795254 A CN202110795254 A CN 202110795254A CN 113507725 A CN113507725 A CN 113507725A
Authority
CN
China
Prior art keywords
rlc entity
data
duration
determining
entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110795254.7A
Other languages
Chinese (zh)
Inventor
白伟华
贺刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202110795254.7A priority Critical patent/CN113507725A/en
Publication of CN113507725A publication Critical patent/CN113507725A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/0858—Load balancing or load distribution among entities in the uplink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0908—Management thereof based on time, e.g. for a critical period only
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data

Abstract

The application discloses a data transmission method and device in a separated bearing mode and terminal equipment, and belongs to the technical field of communication. The method comprises the following steps: acquiring uplink data to be transmitted; acquiring the data caching duration of a first RLC entity and the data caching duration of a second RLC entity; the service cell corresponding to the first RLC entity and the service cell corresponding to the second RLC entity are in a main-auxiliary relationship; and allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity. According to the technical scheme provided by the embodiment of the application, the uplink data are distributed to the first RLC entity and the second RLC entity based on the data buffering duration in the separated bearing mode, so that the reasonable distribution of the uplink data is realized, the stability of data transmission is improved, and the data throughput of a communication network is improved.

Description

Data transmission method and device in separated bearer mode and terminal equipment
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a data transmission method and device in a separated bearer mode and terminal equipment.
Background
With the development of communication technology, 5GS (5th Generation System, fifth Generation mobile communication System) introduces various bearer types, such as Split bearers, MCG (Master Cell Group) bearers, SCG (Secondary Cell Group) bearers, and the like.
Take UE (User Equipment) side data transmission in the split bearer mode as an example. When uplink Data to be transmitted (e.g., uplink Data received by a Packet Data Convergence Protocol (PDCP) entity) exceeds a Data separation threshold, the PDCP entity of the UE may select to allocate the uplink Data to a primary RLC (Radio Link Control) entity or a secondary RLC entity associated with the PDCP entity, and does not restrict the amount of Data allocated by the PDCP entity to the primary RLC entity or the secondary RLC entity.
However, if the primary RLC entity is allocated more uplink data when the data buffering duration of the primary RLC entity is longer, the primary RLC entity may not have time to transmit the uplink data, and the data allocation is not reasonable enough.
Disclosure of Invention
The embodiment of the application provides a data transmission method and device in a split bearer mode and a terminal device, which can reasonably allocate uplink data to an RLC entity associated with a PDCP entity, thereby reducing the time delay of data transmission, improving the stability of data transmission and further improving the data throughput of a communication network. The technical scheme is as follows:
according to an aspect of the embodiments of the present application, there is provided a method for allocating data in a split bearer mode, the method including:
acquiring uplink data to be transmitted;
acquiring the data caching duration of a first Radio Link Control (RLC) entity and the data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship;
and allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
According to an aspect of the embodiments of the present application, there is provided a data distribution apparatus in a split bearer mode, the apparatus including:
the uplink data acquisition module is used for acquiring uplink data to be transmitted;
a buffer duration obtaining module, configured to obtain a data buffer duration of a first radio link control RLC entity and a data buffer duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship;
and the allocation quantity determining module is used for performing allocation processing on the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation quantity of the first RLC entity and the data allocation quantity of the second RLC entity.
According to an aspect of the embodiments of the present application, there is provided a terminal device, where the terminal device includes a processor and a memory, where a computer program is stored in the memory, and the computer program is executed by the processor to implement the data distribution method in the split bearer mode.
According to an aspect of the embodiments of the present application, there is provided a computer-readable storage medium, in which a computer program is stored, the computer program being configured to be executed by a processor to implement the data distribution method in the split bearer mode.
According to an aspect of the embodiments of the present application, there is provided a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs, the chip is configured to implement the data distribution method in the split bearer mode.
According to an aspect of embodiments of the present application, there is provided a computer program product or a computer program, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium, and a processor reading and executing the computer instructions from the computer-readable storage medium, so as to implement the data distribution method in the above-mentioned split bearer mode.
The technical scheme provided by the embodiment of the application can bring the following beneficial effects:
by reasonably distributing the uplink data to the first RLC entity and the second RLC entity based on the data buffering duration of the first RLC entity and the second RLC entity under the separated bearing mode, the reasonable distribution of the uplink data is realized, the problem that the uplink data cannot be transmitted in time due to unreasonable distributed data of the RLC entities in the related art is solved, and the data transmission delay is reduced.
In addition, the uplink data are reasonably distributed, and the RLC entity with a better data transmission environment (such as a shorter data caching time) is used for transmitting the uplink data, so that the data transmission efficiency is ensured, the data transmission stability is improved, and the data throughput of the communication network is further improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a network architecture provided by one embodiment of the present application;
fig. 2 and fig. 3 are architecture diagrams of a terminal device side bearer mode provided in an embodiment of the present application;
fig. 4 is a flowchart of a data transmission method in a split bearer mode according to an embodiment of the present application;
fig. 5 and fig. 6 are schematic diagrams of terminal device side data transmission provided in an embodiment of the present application;
FIG. 7 is a flowchart of a data replication method based on data caching duration according to an embodiment of the present application;
fig. 8 is a block diagram of a data transmission apparatus in a split bearer mode according to an embodiment of the present application;
fig. 9 is a block diagram of a data transmission apparatus in a split bearer mode according to another embodiment of the present application;
fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.
Referring to fig. 1, a schematic diagram of a network architecture according to an embodiment of the present application is shown. The network architecture 100 may include: a terminal device 10, an access network device 20 and a core network device 30.
Terminal equipment 10 may refer to a UE, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user device. Alternatively, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal digital Assistant) 1 assistance, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in 5GS or a terminal device in a PLMN (Pub1ic Land mobile 1e Network) evolved in the future, and the like, and the embodiment of the present application is not limited herein. For convenience of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is usually plural, and one or more terminal devices 10 may be distributed in a cell managed by each access network device 20.
The access network device 20 is a device deployed in an access network to provide a wireless communication function for the terminal device 10. The access network equipment 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different Radio access technologies, names of devices having functions of access network devices may be different, for example, in a 5GS NR (New Radio, New air interface) system, called a gnnodeb (Next Generation Node B) or a gNB; in an LTE (Long Term Evolution) system, it is called eNodeB (evolved Node B) or eNB.
Illustratively, in an LTE system, the Access network device 20 may be E-UTRA (Evolved Universal Terrestrial Radio Access) or one or more enbs in the E-UTRA; in an NR system, the Access Network device 20 may be a RAN (Radio Access Network) or one or more gnbs in the RAN. In the embodiment of the present application, the network device refers to the access network device 20 unless otherwise specified.
As communication technology evolves, the name "access network equipment" may change. For convenience of description, in the embodiment of the present application, the above-mentioned apparatuses providing the terminal device 10 with the wireless communication function are collectively referred to as an access network device. Alternatively, a communication relationship may be established between the terminal device 10 and the core network device 30 through the access network device 20.
The core network device 30 mainly functions to provide user connection, management of users, and bearer completion for services, and provides an interface to an external network as a bearer network. For example, the core network device in the NR system may include an AMF (Access and Mobility Management Function) entity, a UPF (User Plane Function) entity, and an SMF (Session Management Function) entity.
The technical scheme provided by the embodiment of the application can be suitable for an LTE system, an NR system and a subsequent evolution system of a 5G NR system.
In addition, in the embodiment of the present application, both the terminal device 10 and the access device 20 may support an MR-DC (Multi-Radio Dual Connectivity) architecture. For example, the terminal device 10 supports dual connectivity with an eNB and a gNB. Two cell groups are included in the architecture, one master cell group MCG (master cell group associated with master node) and one secondary cell group SCG (secondary cell group associated with secondary node).
The radio bearer of the terminal device 10 may include: MCG bearers, SCG bearers and Split bearers. The technical scheme provided by the application can be suitable for data transmission under a Split bearing model. Optionally, the technical solution provided by the present application may also be applicable to data transmission in an MCG bearer or an SCG bearer mode.
Exemplarily, referring to fig. 2, an architecture diagram of a terminal side bearer mode provided by an embodiment of the present application is shown. The communication network uses EPC (Evolved Packet Core) as a Core network. A path corresponding to the master cell group Bearer 201 (i.e., MCG Bearer) includes a PDCP entity corresponding to the E-UTRA, an RLC entity corresponding to the E-UTRA, and a MAC (Medium Access Control) entity corresponding to the E-UTRA. The path corresponding to the secondary cell group Bearer 203 (i.e., SCG Bearer) includes a PDCP entity corresponding to NR, an RLC entity corresponding to NR, and a MAC entity corresponding to NR. The path corresponding to the Split Bearer 202 (i.e., Split Bearer) includes a PDCP entity corresponding to NR, an RLC entity corresponding to E-UTRA, an RLC entity corresponding to NR, a MAC entity corresponding to E-UTRA, and a MAC entity corresponding to NR.
Exemplarily, refer to fig. 3, which shows an architecture diagram of a terminal side bearer mode provided by another embodiment of the present application. The communication network uses 5GC (5G CORE, 5G CORE network) as a CORE network. The path corresponding to the Master cell group bearer 301 includes a PDCP entity corresponding to NR, an RLC entity corresponding to MN (Master Node), and an MAC entity corresponding to MN. The path corresponding to the Secondary cell group bearer 303 includes a PDCP entity corresponding to NR, an RLC entity corresponding to SN (Secondary Node), and an MAC entity corresponding to SN. The path corresponding to the separation bearer 302 includes a PDCP entity corresponding to NR, an RLC entity corresponding to MN, an RLC entity corresponding to SN, an MAC entity corresponding to MN, and an MAC entity corresponding to SN.
In an exemplary embodiment, referring to fig. 3, in the split bearer mode 302, one PDCP entity corresponding to NR may associate two RLC entities: the RLC entities corresponding to the MN and the SN. When uplink data received by the PDCP entity reaches or exceeds the data separation threshold, the PDCP entity may allocate the uplink data to the RLC entity corresponding to the MN and the RLC entity corresponding to the SN based on respective data buffering durations of the RLC entity corresponding to the MN and the RLC entity corresponding to the SN, transmit the allocated uplink data to a corresponding base station by the RLC entity corresponding to the MN, and transmit the allocated uplink data to the corresponding base station by the RLC entity corresponding to the SN.
Referring to fig. 4, a flowchart of a data transmission method in a split mode according to an embodiment of the present application is shown. The execution subject of each step of the method may be a terminal device, such as the PDCP entity in the terminal device 10 described above. The method comprises the following steps (401-403):
step 401, obtaining uplink data to be transmitted.
In the embodiment of the present application, uplink data refers to data transmitted from a terminal device to a base station. For example, data transferred from a lower layer PDCP entity (terminal device side) to an upper layer PDCP entity (base station side). Alternatively, the uplink data may be any data generated by the terminal device, such as data generated by an application installed in the terminal device (such as an instant conversation application, a video application, an information retrieval application, and the like).
In an example, after acquiring uplink data, the transmission status of the first RLC entity and the transmission status of the second RLC entity may also be determined, and the preliminary determination of the data allocation amount may be performed based on the transmission status of the first RLC entity and the transmission status of the second RLC entity, and the specific contents may be as follows:
1. determining the data quantity of uplink data as the data distribution quantity of a second RLC entity under the condition that the transmission state of the first RLC entity is a punishment state and the transmission state of the second RLC entity is a non-punishment state; wherein the penalty status is used to indicate that the RLC entity is not allocated data for a threshold time.
2. And under the condition that the transmission state of the first RLC entity is a non-penalty state and the transmission state of the second RLC entity is a penalty state, determining the data amount of the uplink data as the data allocation amount of the first RLC entity.
3. In the case that the transmission status of the first RLC entity is non-penalty status and the transmission status of the second RLC entity is non-penalty status, the step of obtaining the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity (i.e., step 402) is performed.
4. And respectively carrying out service cell reselection processing on the first RLC entity and the second RLC entity to reestablish the separated bearer under the condition that the transmission state of the first RLC entity is a punishment state and the transmission state of the second RLC entity is a punishment state.
Optionally, when the terminal device sets the transmission state of the RLC entity to the penalty state, it may set a penalty flag for the RLC entity, that is, it is detected that the RLC entity is marked with the penalty flag, it may determine that the transmission state of the RLC entity is the penalty state, and it is detected that the RLC entity is not marked with the penalty flag, it may determine that the transmission state of the RLC entity is the non-penalty state. In the case that the RLC entity is in the penalty state, the RLC entity is not allocated with uplink data within the threshold time, and the RLC entity can be ignored within the threshold time, and uplink data transmission is performed by another RLC entity.
Optionally, when the transmission state of the RLC entity is set to the penalty state, the terminal device may start a penalty timer, record a duration of the RLC entity in the penalty state through the penalty timer, and if the duration recorded by the penalty timer exceeds the threshold time, remove the penalty of the RLC entity. The threshold time is set according to the type of the terminal device, the data transmission type corresponding to the uplink data, and the like. Optionally, when the air interface signaling indicates bearer reestablishment and release of the terminal device, the penalty of the RLC entity may also be directly removed.
In this embodiment of the present application, if the data caching duration of the RLC entity is greater than the penalty threshold, the transmission state of the RLC entity may be directly set to the penalty state. The penalty threshold is related to the data caching duration, and can be adaptively set and adjusted according to actual needs so as to avoid long-time caching of uplink data. Illustratively, assuming that the penalty threshold is set to a, if the data buffering duration of the RLC entity is greater than a, the transmission status of the RLC entity may be directly set to the penalty status. Optionally, when the RLC entity is penalized, if the data buffering duration of the RLC entity is still greater than or equal to the penalty threshold, the transmission status of the RLC entity is set to the penalty status again. If the data caching duration of the RLC entity is less than the penalty threshold, uplink data can be distributed to the RLC entity.
Optionally, if the transmission state of the first RLC entity is a penalty state, and the transmission state of the second RLC entity is also a penalty state, it indicates that the transmission environments of the channel where the first RLC entity is located and the channel where the second RLC entity is located are both poor and insufficient to support timely transmission of uplink data, and the serving cell may be reselected to expect to obtain a better serving cell, so as to improve the transmission environments of the channel where the first RLC entity is located and the channel where the second RLC entity is located.
Optionally, the data allocation amount refers to a data amount corresponding to uplink data to which the RLC entity is allocated. For example, if the PDCP entity has 100 packets of uplink data, 60 packets of the uplink data are allocated to the first RLC entity, and 40 packets of the uplink data are allocated to the second RLC entity, 60 packets are the data allocation amount of the first RLC entity, and 40 packets are the data allocation amount of the first RLC entity.
Step 402, obtaining a data caching duration of a first RLC entity and a data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a primary-secondary relationship.
The data buffering duration refers to the buffering duration of uplink data in a channel where the RLC entity is located, and each piece of uplink data corresponds to one data buffering duration. Optionally, the difference between the timestamp corresponding to the uplink data with the smallest timestamp in the channel where the RLC entity is located and the current server time is determined as the data caching duration of the RLC entity.
Illustratively, when the PDCP entity allocates uplink data, whether to the first RLC entity or the second RLC entity, the data packets are time-stamped one by one, so as to calculate the buffer duration of each data packet. Assuming that the data caching duration of the RLC entity needs to be acquired at the first time, determining a timestamp corresponding to the uplink data with the smallest timestamp cached in a channel where the RLC entity is located as a target timestamp, and determining a difference between the target timestamp and the first time as the data caching duration of the RLC entity. Optionally, an average value of a buffering duration (i.e., a difference between the corresponding timestamp and the current server time) corresponding to each data packet may also be determined as the data buffering duration of the RLC entity, which is not limited herein.
A serving cell refers to an area covered by a base station or a portion of a base station (e.g., a sector antenna) within which a terminal device may obtain service (e.g., communication). The serving cell corresponding to the RLC entity refers to a serving cell to which the RLC entity is accessed.
In an example, after the data buffering duration corresponding to the first RLC entity and the data buffering duration corresponding to the second RLC entity are obtained, the data allocation amount may be pre-determined, and the specific content may be as follows:
1. and under the condition that the data caching duration of the first RLC entity is smaller than a penalty threshold and the data caching duration of the second RLC entity is larger than the penalty threshold, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
2. And determining the data volume of the uplink data as the data distribution volume of the second RLC entity under the condition that the data caching duration of the first RLC entity is greater than the penalty threshold and the data caching duration of the second RLC entity is less than the penalty threshold.
3. And under the condition that the data caching duration of the first RLC entity is less than a penalty threshold and the data caching duration of the second RLC entity is less than the penalty threshold, executing the step of allocating uplink data based on the data caching duration of the first RLC entity and the data caching duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
4. And respectively carrying out service cell reselection processing on the first RLC entity and the second RLC entity to reestablish the separated bearer under the condition that the data caching duration of the first RLC entity is greater than a penalty threshold and the data caching duration of the second RLC entity is greater than the penalty threshold.
Optionally, if the data buffering duration of the first RLC entity is greater than the penalty threshold, the transmission status of the first RLC entity may be set to the penalty status, that is, uplink data is not allocated to the first RLC entity within the threshold time.
Step 403, performing allocation processing on the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
In one example, the specific determination method of the data allocation amount may be as follows: if the data caching duration of the first RLC entity is longer than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the second RLC entity; and if the data caching duration of the first RLC entity is less than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
If the data caching duration of the first RLC entity is less than the data caching duration of the second RLC entity, the network environment of the channel where the first RLC entity is located is superior to the network environment of the channel where the second RLC entity is located; if the data caching duration of the first RLC entity is longer than the data caching duration of the second RLC entity, the network environment of the channel where the second RLC entity is located is superior to the network environment of the channel where the first RLC entity is located, uplink data are transmitted through the RLC entity with the superior network environment, and the timeliness of uplink data transmission can be guaranteed.
Optionally, the data buffering duration of the first RLC entity may be divided into a case where the data buffering duration of the first RLC entity is less than the data buffering duration of the second RLC entity, or a case where the data buffering duration of the first RLC entity is equal to the data buffering duration of the second RLC entity, or a case where the data buffering duration of the first RLC entity is greater than the data buffering duration corresponding to the second RLC entity.
In another example, the specific determination method of the data allocation amount may be as follows: under the condition that a service cell corresponding to a first RLC entity is a main service cell and a service cell corresponding to a second RLC entity is an auxiliary service cell, acquiring network delay of the second RLC entity, wherein the network delay refers to the network delay between a base station corresponding to the auxiliary service cell and a core network; if the data caching duration of the first RLC entity is greater than the first sum, determining the data volume of the uplink data as the data allocation volume of the second RLC entity; the first sum is the sum of the data caching duration of the second RLC entity and the network delay of the second RLC entity; and if the data caching duration of the first RLC entity is less than the first sum, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
Optionally, the data buffering duration of the first RLC entity may be divided into a case where the data buffering duration of the first RLC entity is less than the first sum, or a case where the data buffering duration of the first RLC entity is equal to the first sum, or a case where the data buffering duration of the first RLC entity is greater than the first sum.
In the embodiment of the application, the influence of the primary and secondary serving cells is considered, the data transmission duration (namely, the network delay) from the base station corresponding to the secondary serving cell to the core network is longer than the data transmission duration from the base station corresponding to the primary serving cell to the core network by one, and the network delay can be 0 to 5 milliseconds according to an empirical value. By considering the influence of the primary and secondary serving cells, the transmission process of the uplink data can be reflected more truly, and thus the uplink data can be accurately distributed.
Optionally, after the data allocation amount is determined, if the buffered data of the target RLC entity reaches the upper buffer limit, suspending the data allocation to the target RLC entity, where the target RLC entity is the first RLC entity and/or the second RLC entity; and if the cached data of the target RLC entity is smaller than the caching upper limit value, distributing the data to the target RLC entity according to the data distribution amount of the target RLC entity.
In an exemplary embodiment, referring to fig. 5, the PDCP entity 501 acquires uplink data and stores it in an RB (Radio Bearer) data queue. Under the condition of receiving a data transmission request sent by an upper layer, determining the data allocation amount of a first RLC entity and a second RLC entity, wherein the specific method comprises the following steps: acquiring the data caching duration of a first RLC entity and the data caching duration of a second RLC entity, and if the data caching duration of the first RLC entity is less than the data caching duration of the second RLC entity, allocating uplink data to the first RLC entity; and if the data caching duration of the first RLC entity is greater than or equal to the data caching duration of the second RLC entity, allocating the uplink data to the second RLC entity. After determining the data allocation amount of the RLC entity, the PDCP entity 501 reads the uplink data in the RB data queue, performs related processing such as protection and ciphering on the uplink data, and then allocates the processed uplink data to the corresponding RLC entity based on the data allocation amount of the RLC entity, and the RLC entity stores the processed uplink data in the data queue. In case that the RLC entity (or MAC entity) receives the uplink grant information, the RLC entity performs transmission of uplink data. Wherein, the PHY (Physical Layer) entity is configured to receive the uplink grant information from the base station and send the uplink grant information to the MAC entity. Optionally, in this embodiment of the present application, the terminal device uses a preprocessing method, that is, the PDCP entity and the RLC entity perform processing such as packing uplink data in advance. The uplink grant information is control information for notifying the terminal device that data transmission is possible, and includes grant information of radio transmission resources available for data uplink, which the base station gives to the terminal device.
Optionally, referring to fig. 6, the terminal device may also not use a preprocessing method, that is, after receiving the uplink authorization information, the PHY entity transmits the uplink authorization information to the MAC entity, the MAC entity transmits the uplink authorization information to the RLC entity, the RLC entity finally transmits the uplink authorization information to the PDCP entity 601, and after receiving the uplink authorization information, the PDCP entity 601 performs uplink data allocation processing based on the data buffering duration. Optionally, after the PDCP entity 601 receives the uplink grant information, the PDCP entity 601 may check the signal quality of a path corresponding to the RLC entity, and if the signal quality satisfies a strength that the uplink data can be successfully transmitted, the uplink data may be allocated to the RLC entity, otherwise, the uplink data is not allocated. Therefore, the frequency of data transmission failure can be reduced, and the problems of data accumulation, SN (Serial Number) disorder corresponding to PDCP and the like can be reduced.
In one example, in the case that a data transmission network is unstable, acquiring a data buffering duration of a first RLC entity and a data buffering duration of a second RLC entity within each transmission time interval TTI;
under the condition that the data caching duration of the first RLC entity is greater than a first threshold value and the data caching duration of the second RLC entity is less than the first threshold value, if the retransmission parameter corresponding to the uplink data is the first threshold value, copying the overtime caching data of the first RLC entity into the second RLC entity; if the retransmission parameter corresponding to the uplink data is a second threshold value, discarding overtime cache data of the first RLC entity; the overtime cache data refers to cache data with the cache time exceeding a first threshold, and the first threshold and the retransmission parameter are determined by a data transmission type corresponding to the uplink data;
under the condition that the data caching duration of a first RLC entity is smaller than a first threshold value and the data caching duration of a second RLC entity is larger than the first threshold value, if a retransmission parameter corresponding to uplink data is the first threshold value, copying overtime caching data of the second RLC entity into the first RLC entity; and if the retransmission parameter corresponding to the uplink data is the second threshold, discarding the overtime cache data of the second RLC entity.
In this case, when the uplink data is not transmitted due to a large fluctuation in the signal strength of the serving cell of the RLC entity, a serving cell handover, or the like, it can be determined that the data transmission network is unstable. For example, in this case, there is a certain probability that a small amount of data will be buffered in the channel where the RLC entity is located for a long time, so that a first threshold value related to the data buffering duration may be set, and if the data buffering duration is greater than the first threshold value, it may be determined that the data transmission network is unstable.
Optionally, the setting method of the first threshold may be as follows: if the data transmission type corresponding to the uplink data belongs to strong real-time (such as long term evolution voice bearing, real-time games and the like), the first threshold value can be set to be smaller; if the data transmission type corresponding to the uplink data belongs to general real-time (e.g., file transfer protocol uploading, web page access, etc.), the first threshold may be set to be larger, and the embodiment of the present application is not limited herein. Optionally, the first threshold may also be set according to factors such as the type of the terminal device, whether the base station has a corresponding configuration, and the like. For example, taking TCP (Transmission Control Protocol) data as an example, the first threshold should not be higher than the maximum retransmission time of the TCP data.
Optionally, the setting method of the retransmission parameter may be as follows: if the data transmission type corresponding to the uplink data is strong in real-time performance, the overtime cache data is not needed any more and can be directly discarded, and then the retransmission parameter can be set to 0 (the data can be discarded); if the data transmission type corresponding to the uplink data belongs to general real-time performance and the overtime cache data needs to be retransmitted, the retransmission parameter may be set to 1 (indicating that the data needs to be retransmitted).
Exemplarily, referring to fig. 7, a first threshold and a retransmission parameter are determined based on a Transmission type of uplink data, and in each TTI (Transmission Time Interval), a PDCP entity checks data buffering durations of a first RLC entity and a second RLC entity, and if the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity do not exceed the first threshold, waits for a next TTI, and continues to check the data buffering durations of the first RLC entity and the second RLC entity in the next TTI; if the data caching duration of the first RLC entity and the data caching duration of the second RLC entity both exceed a first threshold value, waiting for respective transmission of the first RLC entity and the second RLC entity; if one of the data caching duration of the first RLC entity and the data caching duration of the second RLC entity exceeds a first threshold, discarding overtime cached data in the RLC entities exceeding the first threshold under the condition that the retransmission parameter is equal to 0, and copying the overtime cached data in the RLC entities exceeding the first threshold to the RLC entities not exceeding the first threshold under the condition that the retransmission parameter is equal to 1.
In summary, according to the technical scheme provided in the embodiment of the present application, in the split bearer mode, the uplink data is reasonably allocated to the first RLC entity and the second RLC entity based on the data buffering duration of the first RLC entity and the second RLC entity, so that the reasonable allocation of the uplink data is realized, and the problem that the uplink data cannot be transmitted in time due to unreasonable allocated data of the RLC entities in the related art is avoided, thereby reducing the time delay of data transmission.
In addition, the uplink data are reasonably distributed, and the RLC entity with a better data transmission environment (such as a shorter data caching time) is used for transmitting the uplink data, so that the data transmission efficiency is ensured, the data transmission stability is improved, and the data throughput of the communication network is further improved.
In addition, the overtime cache data in the RLC entity is adjusted by setting the first threshold value and the retransmission parameter under the condition that the data transmission network is unstable, so that the long-time cache of the uplink data is avoided, and the time delay of data transmission is further reduced.
In addition, by considering the influence of the main service cell and the auxiliary service cell and additionally considering the network delay between the auxiliary service cell and the core network, the transmission process of the uplink data can be reflected more truly, and thus the uplink data can be distributed more accurately.
In an exemplary embodiment, the data allocation amount may be determined based on a ratio between data buffering durations, and the following description will take a serving cell corresponding to a first RLC entity as a primary serving cell and a serving cell corresponding to a second RLC entity as a secondary serving cell as an example, and specific contents of the following may be:
1. and acquiring uplink data to be transmitted.
2. Acquiring the data caching duration of a first RLC entity and the data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a primary-secondary relationship.
Optionally, the contents of 1 and 2 are the same as those described in the above embodiments, and are not described again here.
3. And acquiring the network delay of the second RLC entity, wherein the network delay refers to the network delay between the base station corresponding to the auxiliary service cell and the core network.
4. Adding the data caching duration of the first RLC entity and the first sum to obtain a second sum; the first sum is a sum of a data buffering duration of the second RLC entity and a network delay of the second RLC entity.
5. The method includes determining a first fraction based on a data buffering duration of a first RLC entity and a second sum, and determining a second fraction based on the first sum and the second sum.
Optionally, a ratio between the data buffering duration of the first RLC entity and the second sum is determined as a first ratio, and a ratio between the first sum and the second sum corresponding to the second RLC entity is determined as a second ratio.
6. And determining the product of the first ratio and the uplink data as the data allocation amount of the second RLC entity, and determining the product of the second ratio and the uplink data as the data allocation amount of the first RLC entity.
Optionally, by allocating less uplink data to the RLC entity with longer data buffering duration and allocating more uplink data to the RLC entity with shorter data buffering duration, the time delay of data transmission can be reduced, and the efficiency of data transmission can be improved.
In an exemplary embodiment, the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity are respectively counted and sent to the PDCP entity, the PDCP entity performs distribution ratio calculation on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity to obtain a distribution ratio between the first RLC entity and the second RLC entity, and then determines the data distribution amount of the first RLC entity and the data distribution amount of the second RLC entity based on the distribution ratio. Illustratively, the allocation ratio between the first RLC entity and the second RLC entity is a: b, the data allocation amount of the first RLC entity is B/(a + B) of the data amount of the uplink data, and the data allocation amount of the second RLC entity is a/(a + B) of the data amount of the uplink data.
Optionally, the allocation ratio may refer to a ratio of a PDU (Protocol Data Unit) corresponding to the PDCP entity, or may refer to a ratio of a Data length, which is not limited herein.
In summary, according to the technical scheme provided in the embodiment of the present application, in the split bearer mode, the uplink data is reasonably allocated to the first RLC entity and the second RLC entity based on the data buffering duration of the first RLC entity and the second RLC entity, so that the reasonable allocation of the uplink data is realized, and the problem that the uplink data cannot be transmitted in time due to unreasonable allocated data of the RLC entities in the related art is avoided, thereby reducing the time delay of data transmission.
In addition, the uplink data are reasonably distributed, and the RLC entity with a better data transmission environment (such as a shorter data caching time) is used for transmitting the uplink data, so that the data transmission efficiency is ensured, the data transmission stability is improved, and the data throughput of the communication network is further improved.
In an exemplary embodiment, the data allocation amount may be determined based on a data allocation coefficient corresponding to the data buffering duration, and the following description will take a serving cell corresponding to the first RLC entity as a primary serving cell and a serving cell corresponding to the second RLC entity as a secondary serving cell as an example, and specific contents of the data allocation amount may be as follows:
1. and acquiring uplink data to be transmitted.
2. Acquiring the data caching duration of a first RLC entity and the data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a primary-secondary relationship.
Optionally, the contents of 1 and 2 are the same as those described in the above embodiments, and are not described again here.
3. And acquiring the network delay of the second RLC entity, wherein the network delay refers to the network delay between the base station corresponding to the auxiliary service cell and the core network.
4. And determining the data distribution coefficient of the second RLC entity based on the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity.
Optionally, the data allocation coefficient and hereinafter the data allocation cardinality are used to determine the desired data allocation amount of the RLC entity. The relationship between the data distribution coefficient and the data caching duration can be adaptively set and adjusted according to the actual application condition.
Illustratively, if the data buffering duration (or the sum of the data buffering duration and the network delay) is greater than or equal to a (i.e., the penalty threshold above), the data allocation coefficient of the RLC entity is 0 (entering the penalty state); if the data caching duration (or the sum of the data caching duration and the network delay) is greater than or equal to B and less than A, the data distribution coefficient of the RLC entity is 0.2; if the data caching duration (or the sum of the data caching duration and the network delay) is greater than or equal to C and less than B, the data distribution coefficient of the RLC entity is 0.4; if the data caching duration (or the sum of the data caching duration and the network delay) is greater than or equal to D and less than C, the data distribution coefficient of the RLC entity is 0.6; if the data caching duration (or the sum of the data caching duration and the network delay) is greater than or equal to E and less than D, the data distribution coefficient of the RLC entity is 0.8; if the data buffering duration (or the sum of the data buffering duration and the network delay) is less than E, the data allocation coefficient of the RLC entity is 1. Wherein A, B, C, D and E are arranged in descending order, and the specific value can be set according to the empirical value.
The data allocation coefficient of the RLC entity can be determined based on the range of the data buffering duration of the RLC entity, or the data allocation coefficient of the RLC entity can be determined based on the range of the sum of the data buffering duration of the RLC entity and the network delay.
5. And acquiring the data allocation base number of the first RLC entity and the data allocation base number of the second RLC entity.
Alternatively, the data allocation base may be determined based on the type of the serving cell. For example, the data allocation base number of the RLC entity corresponding to the primary serving cell is greater than the data allocation base number of the RLC entity corresponding to the secondary serving cell.
6. The expected data allocation amount of the first RLC entity is determined based on a data allocation base of the first RLC entity and a data allocation coefficient of the first RLC entity, and the expected data allocation amount of the second RLC entity is determined based on a data allocation base of the second RLC entity and a data allocation coefficient of the second RLC entity.
Optionally, the expected data allocation amount of the first RLC entity may be obtained by multiplying the data allocation base number of the first RLC entity by the data allocation coefficient corresponding to the data allocation base number. And multiplying the data distribution base number of the second RLC entity by the corresponding data distribution coefficient to obtain the expected data distribution amount of the second RLC entity.
7. In the case that the data buffering duration of the first RLC entity is less than or equal to the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity, the method for determining the data allocation amount of the first RLC entity may be as follows: if the expected data allocation amount of the first RLC entity is larger than the data amount of the uplink data, determining the data amount of the uplink data as the data allocation amount of the first RLC entity; and if the expected data allocation quantity of the first RLC entity is smaller than the data quantity of the uplink data, determining the expected data allocation quantity of the first RLC entity as the data allocation quantity of the first RLC entity.
The method for determining the data allocation amount of the second RLC entity may be as follows: if the expected data allocation amount of the second RLC entity is larger than the difference value of the data amount of the uplink data and the data allocation amount of the first RLC entity, determining the difference value of the data amount of the uplink data and the data allocation amount of the first RLC entity as the data allocation amount of the second RLC entity; and if the expected data allocation quantity of the second RLC entity is smaller than the difference value between the data quantity of the uplink data and the data allocation quantity of the first RLC entity, determining the expected data allocation quantity of the second RLC entity as the data allocation quantity of the second RLC entity.
Optionally, when the data buffering duration of the first RLC entity is greater than the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity, the data allocation amount of the second RLC entity and the data allocation amount of the first RLC entity are successively determined by using the same method. The embodiment of the application ensures the timeliness of data transmission by preferentially ensuring the data allocation amount of the RLC entity with shorter data caching duration.
Alternatively, the case that the expected data allocation amount of the first RLC entity is equal to the data amount of the uplink data may be divided into the case that the expected data allocation amount of the first RLC entity is less than the data amount of the uplink data, or the case that the expected data allocation amount of the first RLC entity is equal to the data amount of the uplink data may be divided into the case that the expected data allocation amount of the first RLC entity is greater than the data amount of the uplink data; the case that the expected data allocation amount of the second RLC entity is equal to the difference between the data allocation amount of the first RLC entity and the data amount of the uplink data may be classified into the case that the expected data allocation amount of the second RLC entity is less than the difference between the data allocation amount of the first RLC entity and the data amount of the uplink data, or the case that the expected data allocation amount of the second RLC entity is equal to the difference between the data allocation amount of the first RLC entity and the data amount of the uplink data may be classified into the case that the expected data allocation amount of the second RLC entity is greater than the difference between the data allocation amount of the first RLC entity and the data amount of the uplink data.
In summary, according to the technical scheme provided in the embodiment of the present application, in the split bearer mode, the uplink data is reasonably allocated to the first RLC entity and the second RLC entity based on the data buffering duration of the first RLC entity and the second RLC entity, so that the reasonable allocation of the uplink data is realized, and the problem that the uplink data cannot be transmitted in time due to unreasonable allocated data of the RLC entities in the related art is avoided, thereby reducing the time delay of data transmission.
In addition, the uplink data are reasonably distributed, and the RLC entity with a better data transmission environment (such as a shorter data caching time) is used for transmitting the uplink data, so that the data transmission efficiency is ensured, the data transmission stability is improved, and the data throughput of the communication network is further improved.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Referring to fig. 8, a block diagram of a data transmission apparatus in a split mode according to an embodiment of the present application is shown. The device has the function of realizing the data transmission method example in the separation mode, and the function can be realized by hardware or by hardware executing corresponding software. The device can be a terminal device and can also be arranged in the terminal device. The apparatus 800 may include: an uplink data obtaining module 801, a buffer duration obtaining module 802, and an allocation amount determining module 803.
An uplink data obtaining module 801, configured to obtain uplink data to be transmitted.
A buffer duration obtaining module 802, configured to obtain a data buffer duration of a first radio link control RLC entity and a data buffer duration of a second RLC entity; and the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship.
An allocation determining module 803, configured to perform allocation processing on the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determine the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
In an exemplary embodiment, the allocation amount determining module 803 is configured to:
if the data caching duration of the first RLC entity is longer than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the second RLC entity;
and if the data caching duration of the first RLC entity is less than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
In an exemplary embodiment, the allocation amount determining module 803 is further configured to:
acquiring the network delay of the second RLC entity under the condition that the serving cell corresponding to the first RLC entity is a main serving cell and the serving cell corresponding to the second RLC entity is an auxiliary serving cell, wherein the network delay refers to the network delay between a base station and a core network corresponding to the auxiliary serving cell;
if the data caching duration of the first RLC entity is greater than a first sum, determining the data volume of the uplink data as the data allocation volume of the second RLC entity; the first sum is the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity;
and if the data caching duration of the first RLC entity is less than the first sum, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
In an exemplary embodiment, the allocation amount determining module 803 is further configured to:
acquiring the network delay of the second RLC entity under the condition that the serving cell corresponding to the first RLC entity is a main serving cell and the serving cell corresponding to the second RLC entity is an auxiliary serving cell, wherein the network delay refers to the network delay between a base station and a core network corresponding to the auxiliary serving cell;
adding the data caching duration of the first RLC entity and the first sum to obtain a second sum; the first sum is the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity;
determining a first ratio based on the data buffering duration of the first RLC entity and the second sum, and determining a second ratio based on the first sum and the second sum;
and determining the product of the first ratio and the uplink data as the data allocation amount of the second RLC entity, and determining the product of the second ratio and the uplink data as the data allocation amount of the first RLC entity.
In an exemplary embodiment, the allocation amount determining module 803 is further configured to:
acquiring the network delay of the second RLC entity under the condition that the serving cell corresponding to the first RLC entity is a main serving cell and the serving cell corresponding to the second RLC entity is an auxiliary serving cell, wherein the network delay refers to the network delay between a base station and a core network corresponding to the auxiliary serving cell;
determining a data distribution coefficient of the first RLC entity based on the data caching duration of the first RLC entity, and determining a data distribution coefficient of the second RLC entity based on the sum of the data caching duration of the second RLC entity and the network delay of the second RLC entity;
acquiring a data distribution base number of the first RLC entity and a data distribution base number of the second RLC entity;
determining an expected data allocation amount of the first RLC entity based on the data allocation base number of the first RLC entity and the data allocation coefficient of the first RLC entity, and determining an expected data allocation amount of the second RLC entity based on the data allocation base number of the second RLC entity and the data allocation coefficient of the second RLC entity;
determining a data allocation amount of the first RLC entity based on the expected data allocation amount of the first RLC entity and the data amount of the uplink data;
determining the data allocation amount of the second RLC entity based on the expected data allocation amount of the second RLC entity, the data allocation amount of the first RLC entity and the data amount of the uplink data.
In an exemplary embodiment, as shown in fig. 9, the apparatus 800 further comprises: an uplink data allocation module 804.
An uplink data allocation module 804, configured to suspend allocating data to a target RLC entity if buffered data of the target RLC entity reaches a buffered upper limit value, where the target RLC entity is the first RLC entity and/or the second RLC entity.
The uplink data allocation module 804 is further configured to allocate data to the target RLC entity according to the data allocation amount of the target RLC entity if the buffered data of the target RLC entity is smaller than the buffer upper limit value.
In an exemplary embodiment, the allocation amount determining module 803 is further configured to:
determining the data volume of the uplink data as the data allocation volume of the first RLC entity under the condition that the data caching duration of the first RLC entity is smaller than a penalty threshold and the data caching duration of the second RLC entity is larger than the penalty threshold;
or, determining the data amount of the uplink data as the data allocation amount of the second RLC entity under the condition that the data caching duration of the first RLC entity is greater than the penalty threshold and the data caching duration of the second RLC entity is less than the penalty threshold;
or, under the condition that the data caching duration of the first RLC entity is smaller than the penalty threshold and the data caching duration of the second RLC entity is smaller than the penalty threshold, performing the step of allocating the uplink data based on the data caching duration of the first RLC entity and the data caching duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity;
or, respectively performing cell reselection on the first RLC entity and the second RLC entity to reestablish the separate bearer under the condition that the data caching duration of the first RLC entity is greater than the penalty threshold and the data caching duration of the second RLC entity is greater than the penalty threshold.
In an exemplary embodiment, the allocation amount determining module 803 is further configured to:
respectively determining the transmission state of the first RLC entity and the transmission state of the second RLC entity;
determining the data volume of the uplink data as the data allocation volume of the second RLC entity under the condition that the transmission state of the first RLC entity is a penalty state and the transmission state of the second RLC entity is a non-penalty state; wherein the penalty status is used to indicate that the RLC entity is not allocated data within a threshold time;
or, when the transmission status of the first RLC entity is the non-penalty status and the transmission status of the second RLC entity is the penalty status, determining the data amount of the uplink data as the data allocation amount of the first RLC entity;
or, under the condition that the transmission state of the first RLC entity is the non-penalty state and the transmission state of the second RLC entity is the non-penalty state, the step of obtaining the data caching duration of the first RLC entity and the data caching duration of the second RLC entity is executed;
or, respectively performing cell reselection on the first RLC entity and the second RLC entity to reestablish the separate bearer when the transmission status of the first RLC entity is the penalty status and the transmission status of the second RLC entity is the penalty status.
In an exemplary embodiment, as shown in fig. 9, the apparatus 800 further comprises: timeout data processing block 805.
The buffering duration obtaining module 802 is further configured to obtain, in each TTI, a data buffering duration of the first RLC entity and a data buffering duration of the second RLC entity in a case where a data transmission network is unstable.
A timeout data processing module 805, configured to copy, when a data caching duration of the first RLC entity is greater than a first threshold and a data caching duration of the second RLC entity is less than the first threshold, the timeout cached data of the first RLC entity into the second RLC entity if a retransmission parameter corresponding to the uplink data is the first threshold; if the retransmission parameter corresponding to the uplink data is a second threshold, discarding the overtime cache data of the first RLC entity; the overtime cache data refers to cache data with a cache time exceeding the first threshold, and the first threshold and the retransmission parameter are determined by a data transmission type corresponding to the uplink data.
The timeout data processing module 805 is further configured to, when the data caching duration of the first RLC entity is smaller than the first threshold and the data caching duration of the second RLC entity is greater than the first threshold, copy the timeout cached data of the second RLC entity to the first RLC entity if the retransmission parameter corresponding to the uplink data is the first threshold; and if the retransmission parameter corresponding to the uplink data is the second threshold, discarding the overtime cache data of the second RLC entity.
In summary, according to the technical scheme provided in the embodiment of the present application, in the split bearer mode, the uplink data is reasonably allocated to the first RLC entity and the second RLC entity based on the data buffering duration of the first RLC entity and the second RLC entity, so that the reasonable allocation of the uplink data is realized, and the problem that the uplink data cannot be transmitted in time due to unreasonable allocated data of the RLC entities in the related art is avoided, thereby reducing the time delay of data transmission.
In addition, the uplink data are reasonably distributed, and the RLC entity with a better data transmission environment (such as a shorter data caching time) is used for transmitting the uplink data, so that the data transmission efficiency is ensured, the data transmission stability is improved, and the data throughput of the communication network is further improved.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Referring to fig. 10, a schematic structural diagram of a terminal device 1000 according to an embodiment of the present application is shown, for example, the terminal device may be configured to execute the data transmission method in the split bearer mode. Specifically, the method comprises the following steps: the terminal device 1000 may include: a processor 1001, a receiver 1002, a transmitter 1003, a memory 1004, and a bus 1005.
The processor 1001 includes one or more processing cores, and the processor 1001 executes various functional applications and information processing by running software programs and modules.
The receiver 1002 and the transmitter 1003 may be implemented as a transceiver 1006, and the transceiver 1006 may be a communication chip.
The memory 1004 is connected to the processor 1001 through a bus 1005.
The memory 1004 may be used for storing a computer program, which the processor 1001 is configured to execute in order to implement the various steps performed by the terminal device in the above-described method embodiments.
Further, the memory 1004 may be implemented by any type or combination of volatile or non-volatile storage devices, including, but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cartridge, magnetic tape, magnetic disk storage or other magnetic storage devices. Wherein:
the processor 1001 is configured to obtain uplink data to be transmitted;
acquiring the data caching duration of a first Radio Link Control (RLC) entity and the data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship;
and allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
For details which are not described in detail in this embodiment, refer to the description in the above embodiments, and are not described herein again.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used for being executed by a processor of a terminal device, so as to implement the data transmission method in the split bearer mode.
Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State drive), or optical disk. The Random Access Memory may include a ReRAM (resistive Random Access Memory) and a DRAM (Dynamic Random Access Memory).
The embodiment of the present application further provides a chip, where the chip includes a programmable logic circuit and/or a program instruction, and when the chip runs on a terminal device, the chip is configured to implement the data transmission method in the split bearer mode.
The embodiment of the present application further provides a computer program product or a computer program, where the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium, and a processor of the terminal device reads and executes the computer instructions from the computer-readable storage medium, so as to implement the data transmission method in the above-mentioned split bearer mode.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: 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. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (13)

1. A method for distributing data in a split bearer mode, the method comprising:
acquiring uplink data to be transmitted;
acquiring the data caching duration of a first Radio Link Control (RLC) entity and the data caching duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship;
and allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity.
2. The method of claim 1, wherein the allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and the determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity comprises:
if the data caching duration of the first RLC entity is longer than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the second RLC entity;
and if the data caching duration of the first RLC entity is less than the data caching duration of the second RLC entity, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
3. The method of claim 1, wherein the serving cell corresponding to the first RLC entity is a primary serving cell, and the serving cell corresponding to the second RLC entity is a secondary serving cell;
the allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity, includes:
acquiring the network delay of the second RLC entity, wherein the network delay refers to the network delay between a base station corresponding to the auxiliary service cell and a core network;
if the data caching duration of the first RLC entity is greater than a first sum, determining the data volume of the uplink data as the data allocation volume of the second RLC entity; the first sum is the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity;
and if the data caching duration of the first RLC entity is less than the first sum, determining the data volume of the uplink data as the data allocation volume of the first RLC entity.
4. The method of claim 1, wherein the serving cell corresponding to the first RLC entity is a primary serving cell, and the serving cell corresponding to the second RLC entity is a secondary serving cell;
the allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity, includes:
acquiring the network delay of the second RLC entity, wherein the network delay refers to the network delay between a base station corresponding to the auxiliary service cell and a core network;
adding the data caching duration of the first RLC entity and the first sum to obtain a second sum; the first sum is the sum of the data buffering duration of the second RLC entity and the network delay of the second RLC entity;
determining a first ratio based on the data buffering duration of the first RLC entity and the second sum, and determining a second ratio based on the first sum and the second sum;
and determining the product of the first ratio and the uplink data as the data allocation amount of the second RLC entity, and determining the product of the second ratio and the uplink data as the data allocation amount of the first RLC entity.
5. The method of claim 1, wherein the serving cell corresponding to the first RLC entity is a primary serving cell, and the serving cell corresponding to the second RLC entity is a secondary serving cell;
the allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity, includes:
acquiring the network delay of the second RLC entity, wherein the network delay refers to the network delay between a base station corresponding to the auxiliary service cell and a core network;
determining a data distribution coefficient of the first RLC entity based on the data caching duration of the first RLC entity, and determining a data distribution coefficient of the second RLC entity based on the sum of the data caching duration of the second RLC entity and the network delay of the second RLC entity;
acquiring a data distribution base number of the first RLC entity and a data distribution base number of the second RLC entity;
determining an expected data allocation amount of the first RLC entity based on the data allocation base number of the first RLC entity and the data allocation coefficient of the first RLC entity, and determining an expected data allocation amount of the second RLC entity based on the data allocation base number of the second RLC entity and the data allocation coefficient of the second RLC entity;
determining a data allocation amount of the first RLC entity based on the expected data allocation amount of the first RLC entity and the data amount of the uplink data;
determining the data allocation amount of the second RLC entity based on the expected data allocation amount of the second RLC entity, the data allocation amount of the first RLC entity and the data amount of the uplink data.
6. The method of claim 1, wherein the allocating the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and after determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity, further comprises:
if the cached data of the target RLC entity reaches the upper limit value of the cache, suspending the data distribution to the target RLC entity, wherein the target RLC entity is the first RLC entity and/or the second RLC entity;
and if the cached data of the target RLC entity is smaller than the cache upper limit value, distributing the data to the target RLC entity according to the data distribution amount of the target RLC entity.
7. The method of claim 1, wherein after obtaining the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, the method further comprises:
determining the data volume of the uplink data as the data allocation volume of the first RLC entity under the condition that the data caching duration of the first RLC entity is smaller than a penalty threshold and the data caching duration of the second RLC entity is larger than the penalty threshold;
or, determining the data amount of the uplink data as the data allocation amount of the second RLC entity under the condition that the data caching duration of the first RLC entity is greater than the penalty threshold and the data caching duration of the second RLC entity is less than the penalty threshold;
or, under the condition that the data caching duration of the first RLC entity is smaller than the penalty threshold and the data caching duration of the second RLC entity is smaller than the penalty threshold, performing the step of allocating the uplink data based on the data caching duration of the first RLC entity and the data caching duration of the second RLC entity, and determining the data allocation amount of the first RLC entity and the data allocation amount of the second RLC entity;
or, respectively performing cell reselection on the first RLC entity and the second RLC entity to reestablish the separate bearer under the condition that the data caching duration of the first RLC entity is greater than the penalty threshold and the data caching duration of the second RLC entity is greater than the penalty threshold.
8. The method of claim 1, further comprising:
respectively determining the transmission state of the first RLC entity and the transmission state of the second RLC entity;
determining the data volume of the uplink data as the data allocation volume of the second RLC entity under the condition that the transmission state of the first RLC entity is a penalty state and the transmission state of the second RLC entity is a non-penalty state; wherein the penalty status is used to indicate that the RLC entity is not allocated data within a threshold time;
or, when the transmission status of the first RLC entity is the non-penalty status and the transmission status of the second RLC entity is the penalty status, determining the data amount of the uplink data as the data allocation amount of the first RLC entity;
or, under the condition that the transmission state of the first RLC entity is the non-penalty state and the transmission state of the second RLC entity is the non-penalty state, the step of obtaining the data caching duration of the first RLC entity and the data caching duration of the second RLC entity is executed;
or, respectively performing cell reselection on the first RLC entity and the second RLC entity to reestablish the separate bearer when the transmission status of the first RLC entity is the penalty status and the transmission status of the second RLC entity is the penalty status.
9. The method according to any one of claims 1 to 8, further comprising:
under the condition that a data transmission network is unstable, acquiring the data caching duration of the first RLC entity and the data caching duration of the second RLC entity in each transmission time interval TTI;
under the condition that the data caching duration of the first RLC entity is greater than a first threshold value and the data caching duration of the second RLC entity is less than the first threshold value, if the retransmission parameter corresponding to the uplink data is a first threshold value, copying the overtime cached data of the first RLC entity into the second RLC entity; if the retransmission parameter corresponding to the uplink data is a second threshold, discarding the overtime cache data of the first RLC entity; the overtime cache data refers to cache data with cache time exceeding the first threshold, and the first threshold and the retransmission parameter are determined by a data transmission type corresponding to the uplink data;
alternatively, the first and second electrodes may be,
under the condition that the data caching duration of the first RLC entity is smaller than the first threshold and the data caching duration of the second RLC entity is larger than the first threshold, if the retransmission parameter corresponding to the uplink data is the first threshold, copying the overtime caching data of the second RLC entity into the first RLC entity; and if the retransmission parameter corresponding to the uplink data is the second threshold, discarding the overtime cache data of the second RLC entity.
10. A data distribution device in a split bearer mode, the device comprising:
the uplink data acquisition module is used for acquiring uplink data to be transmitted;
a buffer duration obtaining module, configured to obtain a data buffer duration of a first radio link control RLC entity and a data buffer duration of a second RLC entity; the serving cell corresponding to the first RLC entity and the serving cell corresponding to the second RLC entity are in a main-auxiliary relationship;
and the allocation quantity determining module is used for performing allocation processing on the uplink data based on the data buffering duration of the first RLC entity and the data buffering duration of the second RLC entity, and determining the data allocation quantity of the first RLC entity and the data allocation quantity of the second RLC entity.
11. A terminal device, characterized in that the terminal device comprises a processor and a memory, in which a computer program is stored, which computer program is executed by the processor to implement the method for data transmission in split bearer mode according to any of claims 1 to 9.
12. A computer-readable storage medium, in which a computer program is stored which is adapted to be executed by a processor to implement the method of data transmission in a split bearer mode according to any one of claims 1 to 9.
13. A chip comprising programmable logic circuitry and/or program instructions for implementing a method of data transmission in a split bearer mode as claimed in any one of claims 1 to 9 when the chip is in operation.
CN202110795254.7A 2021-07-14 2021-07-14 Data transmission method and device in separated bearer mode and terminal equipment Pending CN113507725A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110795254.7A CN113507725A (en) 2021-07-14 2021-07-14 Data transmission method and device in separated bearer mode and terminal equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110795254.7A CN113507725A (en) 2021-07-14 2021-07-14 Data transmission method and device in separated bearer mode and terminal equipment

Publications (1)

Publication Number Publication Date
CN113507725A true CN113507725A (en) 2021-10-15

Family

ID=78013100

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110795254.7A Pending CN113507725A (en) 2021-07-14 2021-07-14 Data transmission method and device in separated bearer mode and terminal equipment

Country Status (1)

Country Link
CN (1) CN113507725A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106063326A (en) * 2013-10-31 2016-10-26 日本电气株式会社 Wireless communication system, base station device, wireless terminal, and communication control method
CN107277853A (en) * 2016-04-07 2017-10-20 华为技术有限公司 A kind of data transmission method and device
CN108809542A (en) * 2017-05-05 2018-11-13 华为技术有限公司 A kind for the treatment of method and apparatus of data transmission
US20190132897A1 (en) * 2017-09-28 2019-05-02 Telefonaktiebolaget Lm Ericsson (Publ) Pdcp ul split and pre-processing
CN110999385A (en) * 2017-06-16 2020-04-10 捷开通讯(深圳)有限公司 Method and apparatus relating to splitting bearers with an uplink in a new radio
CN112788698A (en) * 2020-12-23 2021-05-11 展讯半导体(成都)有限公司 Data processing method and device and terminal equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106063326A (en) * 2013-10-31 2016-10-26 日本电气株式会社 Wireless communication system, base station device, wireless terminal, and communication control method
CN107277853A (en) * 2016-04-07 2017-10-20 华为技术有限公司 A kind of data transmission method and device
CN108809542A (en) * 2017-05-05 2018-11-13 华为技术有限公司 A kind for the treatment of method and apparatus of data transmission
CN110999385A (en) * 2017-06-16 2020-04-10 捷开通讯(深圳)有限公司 Method and apparatus relating to splitting bearers with an uplink in a new radio
US20190132897A1 (en) * 2017-09-28 2019-05-02 Telefonaktiebolaget Lm Ericsson (Publ) Pdcp ul split and pre-processing
CN111386743A (en) * 2017-09-28 2020-07-07 瑞典爱立信有限公司 PDCP UL partitioning and preprocessing
CN112788698A (en) * 2020-12-23 2021-05-11 展讯半导体(成都)有限公司 Data processing method and device and terminal equipment

Similar Documents

Publication Publication Date Title
US11212874B2 (en) Methods and devices associated with direct communications in a radio access network
US10708940B2 (en) Method and apparatus for reporting buffer state by user equipment in communication system
KR101480598B1 (en) Techniques for initiating communication in a wireless network
KR101605293B1 (en) Method for notifying channel utilization time for sending uplink data, uplink data sending method and device
CN108551667B (en) A kind of data dispatching method, base station and system
CN108337633B (en) Data distribution configuration method, base station system and user terminal
CN111264080A (en) Method and apparatus for triggering transmission carrier selection in wireless communication system
JP2002534925A (en) Method of transmitting measurement report in telecommunications system
JP2017508364A (en) Communication method executed by secondary base station and master base station, and corresponding base station
WO2014134785A1 (en) Method, apparatus and system for switching state
WO2020030170A1 (en) Method and device for obtaining scheduled throughput, base station, and storage medium
WO2017147760A1 (en) Data transmission method and system at unlicensed frequency spectrum and terminal device
CN109246833B (en) Bearer configuration determination method, bearer configuration information sending method, bearer configuration determination device, bearer configuration information sending device, main base station and auxiliary base station
JP2000078653A (en) Resource assignment method for radio communication system
US20220240282A1 (en) Methods for information transmission
CN108631959A (en) Communication means, data cell and control unit
EP2942990A1 (en) Method, system and equipment for realizing cluster group call session in long term evolution
CN114531400A (en) Data transmission method and related device
KR102364240B1 (en) Method and apparatus for supporting a network connection of a terminal in a next generation communication system
US11617102B2 (en) User equipment and buffer status report cancellation method based on carrier aggregation and integrated access and backhaul
CN113507725A (en) Data transmission method and device in separated bearer mode and terminal equipment
CN108934079B (en) Resource scheduling method, terminal equipment and network side equipment
TWI762999B (en) User equipment and buffer status report cancellation method based on carrier aggregation and integrated access and backhaul
EP4224919A1 (en) Communication method and apparatus
CN113507726A (en) Data transmission method and device in separated bearer mode and terminal equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination