CN109391934B - Data reporting method and mobile terminal - Google Patents

Data reporting method and mobile terminal Download PDF

Info

Publication number
CN109391934B
CN109391934B CN201710677605.8A CN201710677605A CN109391934B CN 109391934 B CN109391934 B CN 109391934B CN 201710677605 A CN201710677605 A CN 201710677605A CN 109391934 B CN109391934 B CN 109391934B
Authority
CN
China
Prior art keywords
data
bearer
information
logical channel
network side
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.)
Active
Application number
CN201710677605.8A
Other languages
Chinese (zh)
Other versions
CN109391934A (en
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.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co 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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN201710677605.8A priority Critical patent/CN109391934B/en
Publication of CN109391934A publication Critical patent/CN109391934A/en
Application granted granted Critical
Publication of CN109391934B publication Critical patent/CN109391934B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • 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/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • 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/10—Flow control between communication endpoints

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention provides a data reporting method and a mobile terminal, relates to the field of communication, and solves the problems that data transmission is delayed or data cannot be transmitted in the prior art. The method comprises the following steps: acquiring data volume information of service data adaptation protocol SDAP layer cache data; and reporting the data volume information to a network side. The scheme of the invention enables the network side to know the data amount cached by the SDAP layer and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.

Description

Data reporting method and mobile terminal
Technical Field
The present invention relates to the field of communications, and in particular, to a data reporting method and a mobile terminal.
Background
Because the 5G system introduces a network side indication mechanism of QoS (Quality of Service), QoS indication information (such as flow ID) of an IP Data stream of a UE (User Equipment) needs to be added in both the transmission process of uplink and downlink Data, and the Service Data Adaptation Protocol (SDAP) layer is located on a Packet Data Convergence Protocol (PDCP) layer. The 1 SDAP entity corresponds to 1 PDU session (i.e., PDU session), and the 1 SDAP entity may correspond to a plurality of DRBs (Data Radio Bearer) (i.e., a plurality of PDCP entities).
In the 5G system, since a DC (Dual Connectivity) architecture (including two Cell groups, MCG (Master Cell Group) and SCG (Secondary Cell Group)) is adopted and a PDCP copy function is supported, different types of bearer types (bearer types) are generated, including: a standalone bearer, a Split bearer (Split bearer), and a Duplicate bearer (Duplicate bearer). The independent bearer includes an MCG bearer (MCG bearer) and an SCG bearer (SCG bearer).
The MCG carries a corresponding PDCP/RLC (Radio Link Control)/MAC entity (Medium Access Control) entity in the MCG. The SCG carries the corresponding PDCP/RLC/MAC entity in the SCG. The PDCP entity corresponding to the load is separated and carried in 1 cell group, and the corresponding 2 RLC entities and 2 MAC entities are in different cell groups. The duplicate carries 1 PDCP entity correspondingly, and 2 RLC entities and 1 MAC entity are in 1 cell group.
The SDAP layer may have buffered data because it needs to process the transmitted data, and the network side cannot know the amount of the buffered data, which may result in delay of data transmission or failure of data transmission.
Disclosure of Invention
The embodiment of the invention provides a data reporting method and a mobile terminal, which aim to solve the problems of data transmission delay or data transmission incapability in the prior art.
In a first aspect, a data reporting method is provided, including:
acquiring data volume information of service data adaptation protocol SDAP layer cache data;
and reporting the data volume information to a network side.
In a second aspect, a mobile terminal is provided, including:
the acquisition module is used for acquiring the data volume information of the service data adaptation protocol SDAP layer cache data;
and the first reporting module is used for reporting the data volume information to a network side.
In a third aspect, a mobile terminal is provided, which includes a processor, a memory, and a computer program stored on the memory and operable on the processor, and when executed by the processor, the computer program implements the steps of the data reporting method according to any one of the above.
In a fourth aspect, a computer-readable storage medium is provided, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the data reporting method are implemented as in any one of the above.
Therefore, in the embodiment of the invention, the data volume information of the data cached by the SDAP layer is acquired and reported to the network side, so that the network side can acquire the data volume cached by the SDAP layer and help the network side to more accurately schedule the data transmission of the terminal, thereby reducing the data transmission delay, ensuring the normal transmission of the data and avoiding the problems of the data transmission delay or the data transmission failure.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a flowchart of a data reporting method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an independent bearer according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a split bearer according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a replication bearer according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention;
fig. 6 is a second schematic structural diagram of a mobile terminal according to an embodiment of the present invention;
fig. 7 is a third schematic structural diagram of a mobile terminal according to an embodiment of the present invention;
fig. 8 is a fourth schematic structural diagram of a mobile terminal according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In some embodiments of the present invention, a data reporting method is provided, and as shown in fig. 1, the method includes:
step 101, obtaining data volume information of the service data adaptation protocol SDAP layer cache data.
Here, the data volume information of the data cached by the SDAP layer is acquired, so that the data volume information is reported to the network side, and the normal sending of the data is ensured. Wherein, the data amount information of the buffered data stored by the SDAP layer and not sent to the bottom layer protocol entity (such as PDCP) can be counted by the SDAP layer.
Wherein the data volume information includes: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
And step 102, reporting the data volume information to a network side.
Here, the data volume information of the data cached by the SDAP layer is reported to the network side, so that the network side can acquire the data volume cached by the SDAP layer, and the network side is helped to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of the data.
The data reporting method of the embodiment of the invention enables the network side to know the data amount cached by the SDAP layer and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data. The problem that data transmission is delayed or cannot be transmitted is avoided.
Optionally, the step 101 includes:
step 1011, receiving the configuration information sent by the network side.
Here, the network side sends the configuration information to the SDAP layer, so that the SDAP layer can count the data amount information of the cache data according to the configuration information sent by the network side.
Step 1012, obtaining the data size information of the data cached by the SDAP layer according to the configuration information.
Here, the SDAP layer accurately obtains the data volume information of the data cached by the SDAP layer according to the configuration information sent by the network side, so as to report the data volume information to the network side, and ensure the normal sending of the data.
And the corresponding relation between the SDAP entity and other entities can be configured according to the configuration information sent by the network side.
Optionally, the configuration information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Wherein the bearer types include an independent bearer, a split bearer, and a duplicate bearer. The independent bearer includes an MCG bearer and an SCG bearer, and the MCG bearer and the SCG bearer respectively correspond to 1 PDCP entity, 1 RLC entity, and 1 MAC entity. The separated load corresponds to 1 PDCP entity, 2 RLC and 2 MAC entities, the separated load corresponds to 1 PDCP entity in 1 cell group, and 2 RLC and 2 MAC entities in different cell groups. The duplicate bearer corresponds to 1 PDCP entity, 2 RLC and 1 MAC entity, and the duplicate bearer corresponds to 1 PDCP entity, 2 RLC and 1 MAC entity in 1 cell group.
A Logical Channel Group (LCG) may include a plurality of Logical channels, and each Logical Channel corresponds to 1 PDCP entity and 1 RLC entity.
When the bearer type corresponding to the SDAP layer includes only one bearer type, the configuration information sent by the network side may include identification information of a logical channel of each bearer, a logical channel group corresponding to each logical channel, and identification information of each bearer. And the SDAP layer can identify each bearer according to the identification information of each bearer, identify the logic channel of each bearer according to the identification information of the logic channel of each bearer, and identify the logic channel group corresponding to each logic channel. Of course, if the bearer type is a split bearer or a duplicate bearer, the configuration information may further include a logical channel used by the split bearer or the duplicate bearer to send data, so that the SDAP layer can accurately determine the logical channel used by the split bearer or the duplicate bearer to send data.
When the bearer type corresponding to the SDAP layer includes one or more bearer types, the configuration information sent by the network side may include the bearer type of each bearer, identification information of a logical channel of each bearer, a logical channel used for separating bearer transmission data, a logical channel used for duplicating bearer transmission data, a logical channel group corresponding to each logical channel, and identification information of each bearer. The SDAP layer can accurately identify each bearer, accurately acquire the bearer type of each bearer, identify the logical channel of each bearer according to the identification information of the logical channel of each bearer, and accurately determine the logical channel used for separating bearer sending data, the logical channel used for copying bearer sending data and the logical channel group corresponding to each logical channel.
Of course, the application of the configuration information is merely an example, and is not limited thereto.
At this time, the SDAP layer can accurately acquire the data volume information of the cache data of the layer according to the configuration information sent by the network side.
Optionally, the step 101 includes:
and 1013, acquiring data quantity information of the SDAP layer cache data according to rule information agreed with a network side protocol in advance.
The SDAP layer accurately acquires the data volume information of the data cached by the SDAP layer according to the rule information agreed with the protocol of the network side in advance so as to report the data volume information to the network side and ensure the normal sending of the data.
Optionally, the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
When the bearer type corresponding to the SDAP layer includes only one bearer type, the rule information agreed by the protocol may include identification information of a logical channel of each bearer, a logical channel group corresponding to each logical channel, and identification information of each bearer. And the SDAP layer can identify each bearer according to the identification information of each bearer, identify the logic channel of each bearer according to the identification information of the logic channel of each bearer, and identify the logic channel group corresponding to each logic channel. Of course, if the bearer type is a split bearer or a duplicate bearer, the rule information may further include a logical channel used by the split bearer or the duplicate bearer to send data, so that the SDAP layer can accurately determine the logical channel used by the split bearer or the duplicate bearer to send data.
When the bearer type corresponding to the SDAP layer includes one or more bearer types, the rule information agreed by the protocol may include the bearer type of each bearer, identification information of a logical channel of each bearer, a logical channel used for separating bearer to send data, a logical channel used for copying bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer. The SDAP layer can accurately identify each bearer, accurately acquire the bearer type of each bearer, identify the logical channel of each bearer according to the identification information of the logical channel of each bearer, and accurately determine the logical channel used for separating bearer sending data, the logical channel used for copying bearer sending data and the logical channel group corresponding to each logical channel.
Of course, the application of the rule information is merely an example, and is not limited thereto.
At this time, the SDAP layer can accurately acquire the data volume information of the layer cache data according to the rule information agreed by the protocol.
Optionally, the step 102 includes:
and sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the indication information carries the data volume information.
Here, the SDAP layer sends the indication information for reporting the data amount information to the network side to the underlying protocol entity (e.g., MAC entity), and can report the data amount information to the network side according to the indication information by the underlying protocol entity, so that the network side can know the data amount cached by the SDAP layer, and the network side can more accurately schedule the data transmission of the terminal.
Optionally, the step of sending, to the underlying protocol entity, the indication information for reporting the data size information to the network side includes:
step 1021, sending first indication information for reporting the data volume information to a network side to a bottom layer protocol entity, where the data volume information carried by the first indication information is data volume information obtained without distinguishing bearer types.
Here, the bearer type may not be distinguished, and the first indication information for reporting the data volume information to the network side is sent to a bottom layer protocol entity (e.g., a MAC entity), where the data volume information carried by the first indication information is the data volume information obtained without distinguishing the bearer type.
Or
Step 1022, sending second indication information for reporting the data amount information to the network side to the underlying protocol entity, where the data amount information carried by the second indication information is the data amount information acquired according to the bearer type.
Here, the bearer may be distinguished, and second indication information for reporting the data amount information to the network side is sent to a bottom layer protocol entity (e.g., a MAC entity), where the data amount information carried by the second indication information is the data amount information acquired according to the bearer type.
When the bearer type corresponding to the SDAP layer only comprises one bearer type, first indication information for reporting the data volume information to a network side can be sent to a bottom layer protocol entity (such as an MAC entity), namely the bearer type indication is not distinguished; when the bearer type corresponding to the SDAP layer includes one or more bearer types, second indication information, that is, a differentiated bearer indication, for reporting the data volume information to the network side may be sent to a bottom layer protocol entity (e.g., a MAC entity). Of course, the application of the above indication method is merely illustrative and not limited thereto.
The bearer type of each bearer and the logical channel corresponding to each bearer, which correspond to the SDAP layer, may be determined according to the above-mentioned network side configuration information or protocol agreed rule information.
Optionally, the step 1022 includes:
step 10221, sending, to a bottom layer protocol entity corresponding to an independent bearer, second indication information for reporting data amount information corresponding to the independent bearer to a network side, where the data amount information carried by the second indication information includes the data amount information corresponding to the independent bearer.
Here, for the independent bearer, second indication information for reporting the data amount information corresponding to the independent bearer to the network side is sent to a bottom layer protocol entity (such as an MAC entity) corresponding to the independent bearer, where the data amount information carried by the second indication information includes the data amount information corresponding to the independent bearer, and the data amount corresponding to the independent bearer can be reported to the network side through the bottom layer protocol entity according to the second indication information.
For example, as shown in fig. 2, the independent bearers of the terminal include an MCG bearer 201 and an SCG bearer 202, and 1 PDCP entity of the MCG bearer 201 and the SCG bearer 202 corresponds to only 1 RLC entity and 1 MAC entity. 1 logical channel corresponds to 1 RLC and 1 MAC entity of MCG bearer 201, and 1 logical channel corresponds to 1 RLC and 1 MAC entity of SCG bearer 202. And the SDAP layer indicates the data volume information corresponding to MCG bearing to the MAC entity corresponding to MCG bearing, and indicates the data volume information corresponding to SCG bearing to the MAC entity corresponding to SCG bearing.
And/or
Step 10222, sending, to a bottom layer protocol entity corresponding to at least one logical channel used by a separate bearer, second indication information for reporting data volume information corresponding to the separate bearer to a network side, where the data volume information carried by the second indication information includes the data volume information corresponding to the separate bearer.
Here, for the separated bearer, a bottom layer protocol entity (e.g., a MAC entity) corresponding to at least one logical channel used for sending data to the separated bearer sends second indication information for reporting data amount information corresponding to the separated bearer to the network side, where the data amount information carried by the second indication information includes the data amount information corresponding to the separated bearer, and the data amount corresponding to the separated bearer can be reported to the network side through the bottom layer protocol entity according to the second indication information.
For example, as shown in fig. 3, 1 PDCP entity of the first and second split bearers 301 and 302 of the terminal corresponds to 2 RLC entities and 2 MAC entities.
There are 2 logical channels between 2 RLC entities and 2 MAC entities of the first split bearer 301. The first split bearer 301 transmits data through one or both of the logical channels. The SDAP layer indicates the data size information corresponding to the first split bearer 301 to the MAC entity corresponding to the logical channel used by the first split bearer 301 to send data.
There are 2 logical channels between 2 RLC entities and 2 MAC entities of the second split bearer 302. The second split bearer 302 transmits data through one or both of the logical channels. The SDAP layer indicates the data size information corresponding to the second split bearer 302 to the MAC entity corresponding to the logical channel used by the second split bearer 302 to send data.
The logical channel used for separating bearer sending data in the SDAP layer can be determined through the above-mentioned network side configuration information or protocol agreed rule information.
Further, the step 10222 includes:
and if the data sent by the separated bearer only uses one logical channel, sending the data volume information corresponding to the separated bearer to a bottom-layer protocol entity corresponding to the logical channel used by the data sent by the separated bearer, and sending second indication information for reporting the data volume information corresponding to the separated bearer to a network side.
Here, if the separate bearer sends data using only one logical channel, the lower layer protocol entity (e.g., MAC) corresponding to the logical channel used for sending data to the separate bearer sends second indication information for reporting the data size information corresponding to the separate bearer to the network side, and the lower layer protocol entity can report the data size corresponding to the separate bearer to the network side according to the second indication information.
For example, the SDAP layer separates that the bearer corresponds to the data of 10bytes to be sent, and the separated bearer is sent only through a logical channel in the MCG, so that the SDAP layer sends, to the MAC entity in the MCG, second indication information that reports the data amount information of 10bytes corresponding to the separated bearer to the network side, and indicates to the MAC entity in the MCG that the bearer has 10bytes of data to be sent in the SDAP layer.
And if the data sent by the separated bearer uses two logical channels, respectively sending second indication information for reporting the data volume information corresponding to the separated bearer to a network side to two bottom layer protocol entities corresponding to the two logical channels of the separated bearer.
Here, if the separate bearer sends data using two logical channels, second indication information for reporting data amount information corresponding to the separate bearer to the network side is sent to two underlying protocol entities (e.g., MAC) corresponding to the two logical channels of the separate bearer, respectively, and the data amount information corresponding to the separate bearer is reported to the network side through the two underlying protocol entities according to the second indication information.
For example, the SDAP layer separates the bearer to correspond to the data of 10bytes to be sent, and the separated bearer is sent through the logical channel in the MCG and the logical channel in the SCG at the same time, so that the SDAP layer sends, to the MAC entity in the MCG, second indication information that reports the data amount information of 10bytes corresponding to the separated bearer to the network side, indicates that the bearer has 10bytes of data to be sent in the SDAP layer to the MAC entity in the MCG, and simultaneously the SDAP layer sends, to the MAC entity in the SCG, second indication information that reports the data amount information of 10bytes corresponding to the separated bearer to the network side, and indicates that the bearer has 10bytes of data to be sent in the SDAP layer to the MAC entity in the SCG.
And/or
Step 10223, sending, to a bottom layer protocol entity corresponding to a duplicate bearer, second indication information for reporting, to a network side, data volume information corresponding to at least one logical channel used by the duplicate bearer to send data, where the data volume information carried by the second indication information includes data volume information corresponding to at least one logical channel used by the duplicate bearer to send data.
Here, for the duplicate bearer, second indication information for reporting data volume information corresponding to at least one logical channel used by the data sent by the duplicate bearer to the network side is sent to a bottom layer protocol entity (e.g., a MAC entity) corresponding to the duplicate bearer, where the data volume information carried by the second indication information includes data volume information corresponding to at least one logical channel used by the data sent by the duplicate bearer, and the data volume corresponding to the duplicate bearer can be reported to the network side through the bottom layer protocol entity according to the second indication information.
For example, as shown in fig. 4, 1 PDCP of the first duplicate bearer 401 and the second duplicate bearer 402 of the terminal corresponds to 2 RLC entities and 1 MAC entity.
There are 2 logical channels between 2 RLC entities and 1 MAC entity of the first duplicate bearer 401. The first duplicate bearer 401 transmits data through one or both of the logical channels. The SDAP layer indicates, to the MAC entity corresponding to the first duplicate bearer 401, data volume information corresponding to a logical channel used by the first duplicate bearer 401 to send data.
There are 2 logical channels between 2 RLC entities and 1 MAC entity of the second duplicate bearer 402. The second duplicate bearer 402 transmits data through one or both of the logical channels. The SDAP layer indicates, to the MAC entity corresponding to the second duplicate bearer 402, data volume information corresponding to a logical channel used by the second duplicate bearer 402 to send data.
The logical channel used by the duplicated bearer to send data in the SDAP layer may be determined through the above-mentioned network side configuration information or the rule information agreed by the protocol.
Further, the step 10223 includes:
and if the data sent by the duplicated bearer only uses one logical channel, sending second indication information for reporting the data volume information corresponding to the logical channel used by the data sent by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer.
Here, if the duplicated bearer sends data using only one logical channel, second indication information for reporting data size information corresponding to the logical channel used by the duplicated bearer to the network side is sent to a lower layer protocol entity (e.g., MAC) corresponding to the duplicated bearer, and the lower layer protocol entity can report the data size corresponding to the duplicated bearer to the network side according to the second indication information.
For example, two logical channels, namely a logical channel a and a logical channel B, are corresponding between 2 RLC entities and 1 MAC entity of the duplicate bearer, the data of 10bytes to be sent is corresponding to the duplicate bearer in the SDAP layer, and the duplicate bearer only sends the data through the logical channel a, so that the SDAP layer sends, to the MAC entity corresponding to the duplicate bearer, second indication information that reports the data amount information of 10bytes corresponding to the logical channel a of the duplicate bearer to the network side, and indicates to the MAC entity corresponding to the duplicate bearer that the logical channel a of the bearer has 10bytes of data to be sent in the SDAP layer.
And if the data sent by the duplicate bearer uses two logical channels, sending second indication information for reporting the data volume information corresponding to the two logical channels of the duplicate bearer to a bottom-layer protocol entity corresponding to the duplicate bearer.
Here, if the duplicate bearer uses two logical channels for sending data, second indication information for reporting data volume information corresponding to the two logical channels of the duplicate bearer to the network side is sent to a duplicate bearer underlying protocol entity (e.g., MAC), and the data volume information corresponding to the duplicate bearer is reported to the network side by the underlying protocol entity according to the second indication information.
For example, two logical channels of logical channel A and logical channel B are corresponding between 2 RLC entities and 1 MAC entity of the duplicated bearer, the duplicated bearer in the SDAP layer corresponds to 10bytes of data to be sent, and the replication bearer sends data through the logical channel a and the logical channel B, then the SDAP layer sends, to the MAC entity corresponding to the replication bearer, second indication information that reports the data amount information of 10bytes corresponding to the logical channel a of the replication bearer to the network side, indicates that the logical channel a of the bearer of the MAC entity corresponding to the replication bearer has 10bytes of data to send in the SDAP layer, and simultaneously, the SDAP layer sends second indication information for reporting the data volume information of the 10bytes corresponding to the logical channel B of the duplicated bearer to the network side to the MAC entity corresponding to the duplicated bearer, and indicates that the logical channel B of the bearer has 10bytes data to be sent in the SDAP layer to the MAC entity corresponding to the duplicated bearer.
Optionally, after the step of sending the indication information for reporting the data size information to the network side to the underlying protocol entity, the method further includes:
step 103, the underlying protocol entity counts the data volume information carried by the indication information into data volume information corresponding to each logical channel and/or each logical channel group.
Here, the underlying protocol entity counts the data volume information carried by the indication information into the data volume information corresponding to each logical channel and/or each logical channel group, so as to report the data volume information corresponding to each logical channel and/or each logical channel group to the network side.
The underlying protocol entity may be, for example, a MAC entity. And the MAC entity counts the data volume information carried by the indication information into the data volume information corresponding to each logical channel and/or each logical channel group.
And step 104, the underlying protocol entity reports the data volume information corresponding to each logical channel and/or each logical channel group to the network side through a buffer data report BSR.
Here, when a bottom layer protocol entity (e.g., a MAC entity) triggers a BSR (Buffer Status Report), data amount information corresponding to each logical channel and/or each logical channel group is reported to the network side.
The MAC entity may count the data volume information cached in the PDCP layer, the RLC layer, and the SDAP layer to the data volume information corresponding to each logical channel and/or each logical channel group, and then report the total data volume information corresponding to each logical channel and/or each logical channel group to the network side.
At this moment, the SDAP layer counts the cached data volume information and indicates different data volume information to the MAC layer according to the bearing type, and the MAC layer counts the data volume information of the SDAP layer when reporting the BSR, so that the network side can know the data volume cached by the SDAP layer and help the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
The data reporting method of the embodiment of the invention enables the network side to know the data amount cached by the SDAP layer and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
In some embodiments of the present invention, as illustrated with reference to fig. 5, a mobile terminal 500 is also provided. The mobile terminal 500 includes:
an obtaining module 501, configured to obtain data size information of service data adaptation protocol SDAP layer cache data;
a first reporting module 502, configured to report the data size information to a network side.
The mobile terminal 500 of the embodiment of the invention enables the network side to know the data amount cached by the SDAP layer, and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
Optionally, referring to fig. 6, the obtaining module 501 includes:
the receiving submodule 5011 is configured to receive configuration information sent by a network side;
the first obtaining sub-module 5012 is configured to obtain data amount information of the data cached by the SDAP layer according to the configuration information.
Optionally, the configuration information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the obtaining module 501 includes:
and the second obtaining submodule is used for obtaining the data volume information of the SDAP layer cache data according to the rule information agreed with the network side protocol in advance.
Optionally, the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the first reporting module 502 is specifically configured to:
and sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the indication information carries the data volume information.
Optionally, the first reporting module 502 includes:
a first sending submodule 5021, configured to send, to a bottom layer protocol entity, first indication information for reporting the data volume information to a network side, where the data volume information carried in the first indication information is data volume information obtained without distinguishing bearer types; or
The second sending submodule 5022 is configured to send, to a bottom layer protocol entity, second indication information for reporting the data volume information to a network side, where the data volume information carried in the second indication information is the data volume information obtained according to the bearer type.
Optionally, the second sending sub-module 5022 includes:
a first sending unit 50221, configured to send, to a bottom-layer protocol entity corresponding to an independent bearer, second indication information for reporting data amount information corresponding to the independent bearer to a network side, where the data amount information carried in the second indication information includes data amount information corresponding to the independent bearer; and/or
A second sending unit 50222, configured to send, to a bottom-layer protocol entity corresponding to at least one logical channel used for sending data to a separate bearer, second indication information for reporting data amount information corresponding to the separate bearer to a network side, where the data amount information carried in the second indication information includes the data amount information corresponding to the separate bearer; and/or
A third sending unit 50223, configured to send, to a bottom-layer protocol entity corresponding to a duplicate bearer, second indication information that reports data volume information corresponding to at least one logical channel used by the duplicate bearer to a network side, where the data volume information carried in the second indication information includes data volume information corresponding to at least one logical channel used by the duplicate bearer to send data.
Optionally, the second transmitting unit 50222 includes:
a first sending subunit, configured to send, if the data sent by the separate bearer only uses one logical channel, a bottom-layer protocol entity corresponding to the logical channel used for sending the data to the separate bearer, and send second indication information that reports data volume information corresponding to the separate bearer to a network side;
and a second sending subunit, configured to send, if the separate bearer sends data using two logical channels, second indication information for reporting the data size information corresponding to the separate bearer to a network side, to two underlying protocol entities corresponding to the two logical channels of the separate bearer respectively.
Optionally, the third transmitting unit 50223 includes:
a third sending subunit, configured to send, to a bottom layer protocol entity corresponding to the duplicate bearer, second indication information that reports, to a network side, data volume information corresponding to one logical channel used by the duplicate bearer to send data, if the duplicate bearer sends data using only one logical channel;
and a fourth sending subunit, configured to send, to a bottom layer protocol entity corresponding to the duplicate bearer, second indication information that reports data volume information corresponding to the two logical channels of the duplicate bearer to a network side, if the duplicate bearer uses two logical channels to send data.
Optionally, the method further includes:
a counting module 503, configured to send, to a bottom layer protocol entity, indication information for reporting the data amount information to a network side, where the bottom layer protocol entity counts the data amount information carried in the indication information in data amount information corresponding to each logical channel and/or each logical channel group;
a second reporting module 504, configured to report, by the underlying protocol entity, the data volume information corresponding to each logical channel and/or each logical channel group to a network side through a buffer data report BSR.
Optionally, the data amount information includes: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
The terminal embodiment of the present invention can implement each step in the method embodiments of fig. 1 to fig. 4, and is not described herein again to avoid repetition. The mobile terminal 500 of the embodiment of the invention enables the network side to know the data amount cached by the SDAP layer, and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
The embodiment of the present invention further provides a mobile terminal, which includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, where the computer program, when executed by the processor, implements each process of the data reporting method embodiment, and can achieve the same technical effect, and is not described herein again to avoid repetition.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the data reporting method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
Fig. 7 is a block diagram of a mobile terminal of one embodiment of the present invention. The mobile terminal 700 shown in fig. 7 includes: at least one processor 701, memory 702, at least one network interface 704, and other user interfaces 703. The various components in the mobile terminal 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable communications among the components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various busses are labeled in figure 7 as the bus system 705.
The user interface 703 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, etc.).
It is to be understood that the memory 702 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 702 of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
In some embodiments, memory 702 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 7021 and application programs 7022.
The operating system 7021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks. The application 7022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. Programs that implement methods in accordance with embodiments of the present invention can be included within application program 7022.
In the embodiment of the present invention, the mobile terminal 700 further includes: a computer program stored on the memory 702 and executable on the processor 701, the computer program when executed by the processor 701 performing the steps of: acquiring data volume information of service data adaptation protocol SDAP layer cache data; and reporting the data volume information to a network side.
The method disclosed in the above embodiments of the present invention may be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 701. The Processor 701 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may reside in ram, flash memory, rom, prom, or eprom, registers, among other computer-readable storage media known in the art. The computer readable storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702, and performs the steps of the above method in combination with the hardware thereof. Specifically, the computer readable storage medium has a computer program stored thereon, and the computer program realizes the steps of the embodiments of the web page display method described above when being executed by the processor 701.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions of the present Application, or a combination thereof.
For a software implementation, the techniques herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
Optionally, the computer program may further implement the following steps when executed by the processor 701: receiving configuration information sent by a network side; and acquiring the data volume information of the SDAP layer cache data according to the configuration information.
Optionally, the configuration information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the computer program may further implement the following steps when executed by the processor 701: and acquiring the data volume information of the SDAP layer cache data according to rule information agreed with a network side protocol in advance.
Optionally, the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the computer program may further implement the following steps when executed by the processor 701: and sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the indication information carries the data volume information.
Optionally, the computer program may further implement the following steps when executed by the processor 701: sending first indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the first indication information is the data volume information obtained without distinguishing the bearing type; or sending second indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the second indication information is the data volume information acquired according to the bearing type.
Optionally, the computer program may further implement the following steps when executed by the processor 701: sending second indication information for reporting the data volume information corresponding to the independent bearer to a network side to a bottom layer protocol entity corresponding to the independent bearer, wherein the data volume information carried by the second indication information comprises the data volume information corresponding to the independent bearer; and/or sending a second indication message for reporting the data volume information corresponding to the separated bearer to a network side to a bottom layer protocol entity corresponding to at least one logical channel used for sending data to the separated bearer, wherein the data volume information carried by the second indication message comprises the data volume information corresponding to the separated bearer; and/or sending second indication information for reporting data volume information corresponding to at least one logical channel used by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer, wherein the data volume information carried by the second indication information includes data volume information corresponding to at least one logical channel used by the duplicated bearer to send data.
Optionally, the computer program may further implement the following steps when executed by the processor 701: if the data sent by the separated bearer only uses one logical channel, sending a bottom layer protocol entity corresponding to the logical channel used by the data sent by the separated bearer to a network side by sending data volume information corresponding to the separated bearer; and if the data sent by the separated bearer uses two logical channels, respectively sending second indication information for reporting the data volume information corresponding to the separated bearer to a network side to two bottom layer protocol entities corresponding to the two logical channels of the separated bearer.
Optionally, the computer program may further implement the following steps when executed by the processor 701: if the data sent by the duplicated bearer only uses one logical channel, sending second indication information for reporting data volume information corresponding to the logical channel used by the data sent by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer; and if the data sent by the duplicate bearer uses two logical channels, sending second indication information for reporting the data volume information corresponding to the two logical channels of the duplicate bearer to a bottom-layer protocol entity corresponding to the duplicate bearer.
Optionally, the computer program may further implement the following steps when executed by the processor 701: after sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, the bottom layer protocol entity counts the data volume information carried by the indication information into data volume information corresponding to each logical channel and/or each logical channel group; and the bottom layer protocol entity reports the data volume information corresponding to each logic channel and/or each logic channel group to a network side through a buffer data report (BSR).
Optionally, the data amount information includes: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
The mobile terminal 700 can implement the processes implemented by the mobile terminal in the foregoing embodiments, and details are not repeated here to avoid repetition. The mobile terminal 700 enables the network side to know the data amount cached by the SDAP layer, and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
Fig. 8 is a schematic structural diagram of a mobile terminal according to another embodiment of the present invention. Specifically, the mobile terminal 800 in fig. 8 may be a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), or a vehicle-mounted computer.
The mobile terminal 800 in fig. 8 includes a Radio Frequency (RF) circuit 810, a memory 820, an input unit 830, a display unit 840, a processor 860, an audio circuit 870, a wifi (wireless fidelity) module 880, and a power supply 890.
The input unit 830 may be used, among other things, to receive numeric or character information input by a user and to generate signal inputs related to user settings and function control of the mobile terminal 800. Specifically, in the embodiment of the present invention, the input unit 830 may include a touch panel 831. The touch panel 831, also referred to as a touch screen, can collect touch operations performed by a user on or near the touch panel 831 (e.g., operations performed by the user on the touch panel 831 using a finger, a stylus, or any other suitable object or accessory), and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 831 may include two portions, i.e., a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 860, and can receive and execute commands sent by the processor 860. In addition, the touch panel 831 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 831, the input unit 830 may include other input devices 832, and the other input devices 832 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
Among other things, the display unit 840 may be used to display information input by the user or information provided to the user and various menu interfaces of the mobile terminal 800. The display unit 840 may include a display panel 841, and the display panel 841 may be alternatively configured in the form of an LCD or an Organic Light-Emitting Diode (OLED), or the like.
It should be noted that the touch panel 831 can overlay the display panel 841 to form a touch display screen, which, when it detects a touch operation thereon or nearby, is passed to the processor 860 to determine the type of touch event, and then the processor 860 provides a corresponding visual output on the touch display screen according to the type of touch event.
The touch display screen comprises an application program interface display area and a common control display area. The arrangement modes of the application program interface display area and the common control display area are not limited, and can be an arrangement mode which can distinguish two display areas, such as vertical arrangement, left-right arrangement and the like. The application interface display area may be used to display an interface of an application. Each interface may contain at least one interface element such as an icon and/or widget desktop control for an application. The application interface display area may also be an empty interface that does not contain any content. The common control display area is used for displaying controls with high utilization rate, such as application icons like setting buttons, interface numbers, scroll bars, phone book icons and the like.
The processor 860 is a control center of the mobile terminal 800, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions of the mobile terminal 800 and processes data by operating or executing software programs and/or modules stored in the first memory 821 and calling data stored in the second memory 822, thereby integrally monitoring the mobile terminal 800. Optionally, processor 860 may include one or more processing units.
In this embodiment of the present invention, the mobile terminal 800 further includes: a computer program stored on the memory 820 and executable on the processor 860, the computer program when executed by the processor 860 performing the steps of: acquiring data volume information of service data adaptation protocol SDAP layer cache data; and reporting the data volume information to a network side.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: receiving configuration information sent by a network side; and acquiring the data volume information of the SDAP layer cache data according to the configuration information.
Optionally, the configuration information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: and acquiring the data volume information of the SDAP layer cache data according to rule information agreed with a network side protocol in advance.
Optionally, the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer to send data, a logical channel used for duplicating bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: and sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the indication information carries the data volume information.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: sending first indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the first indication information is the data volume information obtained without distinguishing the bearing type; or sending second indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the second indication information is the data volume information acquired according to the bearing type.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: sending second indication information for reporting the data volume information corresponding to the independent bearer to a network side to a bottom layer protocol entity corresponding to the independent bearer, wherein the data volume information carried by the second indication information comprises the data volume information corresponding to the independent bearer; and/or sending a second indication message for reporting the data volume information corresponding to the separated bearer to a network side to a bottom layer protocol entity corresponding to at least one logical channel used for sending data to the separated bearer, wherein the data volume information carried by the second indication message comprises the data volume information corresponding to the separated bearer; and/or sending second indication information for reporting data volume information corresponding to at least one logical channel used by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer, wherein the data volume information carried by the second indication information includes data volume information corresponding to at least one logical channel used by the duplicated bearer to send data.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: if the data sent by the separated bearer only uses one logical channel, sending a bottom layer protocol entity corresponding to the logical channel used by the data sent by the separated bearer to a network side by sending data volume information corresponding to the separated bearer; and if the data sent by the separated bearer uses two logical channels, respectively sending second indication information for reporting the data volume information corresponding to the separated bearer to a network side to two bottom layer protocol entities corresponding to the two logical channels of the separated bearer.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: if the data sent by the duplicated bearer only uses one logical channel, sending second indication information for reporting data volume information corresponding to the logical channel used by the data sent by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer; and if the data sent by the duplicate bearer uses two logical channels, sending second indication information for reporting the data volume information corresponding to the two logical channels of the duplicate bearer to a bottom-layer protocol entity corresponding to the duplicate bearer.
Optionally, the computer program when executed by the processor 860 may further implement the steps of: after sending indication information for reporting the data volume information to a network side to a bottom layer protocol entity, the bottom layer protocol entity counts the data volume information carried by the indication information into data volume information corresponding to each logical channel and/or each logical channel group; and the bottom layer protocol entity reports the data volume information corresponding to each logic channel and/or each logic channel group to a network side through a buffer data report (BSR).
Optionally, the data amount information includes: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
As can be seen, the mobile terminal 800 enables the network side to know the data amount cached by the SDAP layer, and helps the network side to more accurately schedule the data transmission of the terminal, thereby reducing the delay of data transmission and ensuring the normal transmission of data.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (22)

1. A data reporting method is characterized by comprising the following steps:
acquiring data volume information of service data adaptation protocol SDAP layer cache data;
reporting the data volume information to a network side;
the step of reporting the data volume information to the network side comprises the following steps:
sending indication information for reporting the data volume information to a network side to a bottom protocol entity, wherein the indication information carries the data volume information;
after the step of sending the indication information for reporting the data volume information to the network side to the underlying protocol entity, the method further includes:
the bottom layer protocol entity counts the data volume information carried by the indication information into the data volume information corresponding to each logical channel and/or each logical channel group;
and the bottom layer protocol entity reports the data volume information corresponding to each logic channel and/or each logic channel group to a network side through a buffer data report (BSR).
2. The data reporting method of claim 1, wherein the step of obtaining the data volume information of the SDAP layer buffer data comprises:
receiving configuration information sent by a network side;
and acquiring the data volume information of the SDAP layer cache data according to the configuration information.
3. The data reporting method of claim 2, wherein the configuration information comprises: at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearer transmission data, a logical channel used for duplicating bearer transmission data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
4. The data reporting method of claim 1, wherein the step of obtaining the data volume information of the SDAP layer buffer data comprises:
and acquiring the data volume information of the SDAP layer cache data according to rule information agreed with a network side protocol in advance.
5. The data reporting method of claim 4, wherein the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used for separating bearers to send data, a logical channel used for duplicating bearers to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
6. The method according to claim 1, wherein the step of sending the indication information for reporting the data amount information to the network side to the underlying protocol entity comprises:
sending first indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the first indication information is the data volume information obtained without distinguishing the bearing type; or
And sending second indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the second indication information is the data volume information acquired according to the bearing type.
7. The method according to claim 6, wherein the step of sending second indication information for reporting the data size information to the network side to the underlying protocol entity comprises:
sending second indication information for reporting the data volume information corresponding to the independent bearer to a network side to a bottom layer protocol entity corresponding to the independent bearer, wherein the data volume information carried by the second indication information comprises the data volume information corresponding to the independent bearer; and/or
Sending second indication information for reporting data volume information corresponding to a separated bearer to a network side to a bottom layer protocol entity corresponding to at least one logic channel used for sending data to the separated bearer, wherein the data volume information carried by the second indication information comprises the data volume information corresponding to the separated bearer; and/or
And sending second indication information for reporting data volume information corresponding to at least one logic channel used by the data sent by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer, wherein the data volume information carried by the second indication information comprises the data volume information corresponding to the at least one logic channel used by the data sent by the duplicated bearer.
8. The data reporting method of claim 7, wherein the step of sending the second indication information for reporting the data size information corresponding to the separate bearer to the network side to a bottom layer protocol entity corresponding to at least one logical channel used for sending data to the separate bearer comprises:
if the data sent by the separated bearer only uses one logical channel, sending a bottom layer protocol entity corresponding to the logical channel used by the data sent by the separated bearer to a network side by sending data volume information corresponding to the separated bearer;
and if the data sent by the separated bearer uses two logical channels, respectively sending second indication information for reporting the data volume information corresponding to the separated bearer to a network side to two bottom layer protocol entities corresponding to the two logical channels of the separated bearer.
9. The data reporting method of claim 7, wherein the step of sending, to a bottom layer protocol entity corresponding to a duplicate bearer, second indication information for reporting, to a network side, data volume information corresponding to at least one logical channel used by the duplicate bearer to send data includes:
if the data sent by the duplicated bearer only uses one logical channel, sending second indication information for reporting data volume information corresponding to the logical channel used by the data sent by the duplicated bearer to a network side to a bottom layer protocol entity corresponding to the duplicated bearer;
and if the data sent by the duplicate bearer uses two logical channels, sending second indication information for reporting the data volume information corresponding to the two logical channels of the duplicate bearer to a bottom-layer protocol entity corresponding to the duplicate bearer.
10. The data reporting method of claim 1, wherein the data amount information comprises: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
11. A mobile terminal, comprising:
the acquisition module is used for acquiring the data volume information of the service data adaptation protocol SDAP layer cache data;
the first reporting module is used for reporting the data volume information to a network side;
the first reporting module is specifically configured to:
sending indication information for reporting the data volume information to a network side to a bottom protocol entity, wherein the indication information carries the data volume information;
a counting module, configured to send, to a bottom layer protocol entity, indication information for reporting the data amount information to a network side, where the bottom layer protocol entity counts the data amount information carried in the indication information to data amount information corresponding to each logical channel and/or each logical channel group;
and the second reporting module is used for reporting the data volume information corresponding to each logical channel and/or each logical channel group to the network side by the underlying protocol entity through a buffer data report (BSR).
12. The mobile terminal of claim 11, wherein the obtaining module comprises:
the receiving submodule is used for receiving the configuration information sent by the network side;
and the first obtaining submodule is used for obtaining the data volume information of the SDAP layer cache data according to the configuration information.
13. The mobile terminal of claim 12, wherein the configuration information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used by a separate bearer to send data, a logical channel used by a duplicate bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
14. The mobile terminal of claim 11, wherein the obtaining module comprises:
and the second obtaining submodule is used for obtaining the data volume information of the SDAP layer cache data according to the rule information agreed with the network side protocol in advance.
15. The mobile terminal of claim 14, wherein the rule information includes at least one of a bearer type of each bearer corresponding to the SDAP layer, identification information of a logical channel of each bearer corresponding to the SDAP layer, a logical channel used by a separate bearer to send data, a logical channel used by a duplicate bearer to send data, a logical channel group corresponding to each logical channel, and identification information of each bearer corresponding to the SDAP layer.
16. The mobile terminal of claim 11, wherein the first reporting module comprises:
a first sending submodule, configured to send, to a bottom layer protocol entity, first indication information for reporting the data volume information to a network side, where the data volume information carried in the first indication information is data volume information obtained without distinguishing a bearer type; or
And the second sending submodule is used for sending second indication information for reporting the data volume information to a network side to a bottom layer protocol entity, wherein the data volume information carried by the second indication information is the data volume information acquired according to the bearing type.
17. The mobile terminal of claim 16, wherein the second sending submodule comprises:
a first sending unit, configured to send, to a bottom layer protocol entity corresponding to an independent bearer, second indication information for reporting data volume information corresponding to the independent bearer to a network side, where the data volume information carried in the second indication information includes the data volume information corresponding to the independent bearer; and/or
A second sending unit, configured to send, to a bottom-layer protocol entity corresponding to at least one logical channel used for sending data to a separate bearer, second indication information for reporting data amount information corresponding to the separate bearer to a network side, where the data amount information carried in the second indication information includes the data amount information corresponding to the separate bearer; and/or
A third sending unit, configured to send, to a bottom layer protocol entity corresponding to a duplicate bearer, second indication information that reports, to a network side, data volume information corresponding to at least one logical channel used by the duplicate bearer to send data, where the data volume information carried in the second indication information includes data volume information corresponding to at least one logical channel used by the duplicate bearer to send data.
18. The mobile terminal according to claim 17, wherein the second transmitting unit comprises:
a first sending subunit, configured to send, if the data sent by the separate bearer only uses one logical channel, a bottom-layer protocol entity corresponding to the logical channel used for sending the data to the separate bearer, and send second indication information that reports data volume information corresponding to the separate bearer to a network side;
and a second sending subunit, configured to send, if the separate bearer sends data using two logical channels, second indication information for reporting the data size information corresponding to the separate bearer to a network side, to two underlying protocol entities corresponding to the two logical channels of the separate bearer respectively.
19. The mobile terminal according to claim 17, wherein the third transmitting unit comprises:
a third sending subunit, configured to send, to a bottom layer protocol entity corresponding to the duplicate bearer, second indication information that reports, to a network side, data volume information corresponding to one logical channel used by the duplicate bearer to send data, if the duplicate bearer sends data using only one logical channel;
and a fourth sending subunit, configured to send, to a bottom layer protocol entity corresponding to the duplicate bearer, second indication information that reports data volume information corresponding to the two logical channels of the duplicate bearer to a network side, if the duplicate bearer uses two logical channels to send data.
20. The mobile terminal of claim 11, wherein the data volume information comprises: at least one of the data quantity of protocol data unit PDU, the data quantity of total service data unit SDU, the data quantity of total PDU, the data quantity of SDU corresponding to each data stream, the data quantity of SDU corresponding to each bearer/logic channel, the data quantity of PDU corresponding to each bearer/logic channel, the data quantity of SDU corresponding to each logic channel group, the data quantity of PDU corresponding to each logic channel group, the sum of data quantity of SDU and PDU corresponding to each bearer/logic channel, and the sum of data quantity of SDU and PDU corresponding to each logic channel group.
21. A mobile terminal, characterized in that it comprises a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data reporting method according to any one of claims 1 to 10.
22. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the data reporting method according to any one of claims 1 to 10.
CN201710677605.8A 2017-08-09 2017-08-09 Data reporting method and mobile terminal Active CN109391934B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710677605.8A CN109391934B (en) 2017-08-09 2017-08-09 Data reporting method and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710677605.8A CN109391934B (en) 2017-08-09 2017-08-09 Data reporting method and mobile terminal

Publications (2)

Publication Number Publication Date
CN109391934A CN109391934A (en) 2019-02-26
CN109391934B true CN109391934B (en) 2022-01-04

Family

ID=65414166

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710677605.8A Active CN109391934B (en) 2017-08-09 2017-08-09 Data reporting method and mobile terminal

Country Status (1)

Country Link
CN (1) CN109391934B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106921996A (en) * 2017-05-12 2017-07-04 电信科学技术研究院 A kind of statistical method of the statistic of layer 2, CU and DU

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7469185B2 (en) * 2002-02-04 2008-12-23 Ocimum Biosolutions, Inc. Primary rat hepatocyte toxicity modeling
JP5213724B2 (en) * 2006-02-03 2013-06-19 ノキア コーポレイション Apparatus, method and computer program for providing buffer status report based on threshold from user equipment to wireless network
CN101873704A (en) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 Method, system and equipment for resource scheduling in long-term evolution system
US8666448B2 (en) * 2011-04-25 2014-03-04 Intel Corporation Headless external sensor discovery and data access using mobile device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106921996A (en) * 2017-05-12 2017-07-04 电信科学技术研究院 A kind of statistical method of the statistic of layer 2, CU and DU

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Data forwarding with QoS flow relocation;Huawei;《3GPP TSG-RAN3 Meeting #95bis R3-171072》;20170325;第1-6页 *

Also Published As

Publication number Publication date
CN109391934A (en) 2019-02-26

Similar Documents

Publication Publication Date Title
JP6526919B2 (en) Method, apparatus and mobile terminal for screen mirroring
CN108008890B (en) Double-screen mobile terminal, cross-application quick transmission method thereof and readable storage medium
CN109150425B (en) Data processing method, mobile terminal and computer readable storage medium
US9894500B2 (en) Status information update method and mobile terminal
US9413874B2 (en) Electronic device, control method, and control program
CN109392097B (en) Data transmission method and device
CN108632901B (en) Data transmission method and terminal
US20200169888A1 (en) Method and device for integrity protection
US20180314383A1 (en) Pressure Touch Control Method and Electronic Device
CN108809561B (en) Transmission method of synchronization signal block, network equipment and user equipment
CN107454664B (en) Data transmission method and mobile terminal
US20150253943A1 (en) Method and Apparatus for Implementing Remote Browsing
CN109801136B (en) Food ordering method, system, terminal, server and medium for preventing malicious ordering
US11546788B2 (en) Configuration method and device of measurement reporting, measurement reporting method and device
WO2019196896A1 (en) Resource scheduling method, information transmission method, network device and terminal
US20200260480A1 (en) Random access method, ue, and base station
CN110140366B (en) Long short message sending method and terminal
CN107615826B (en) Method for determining network type in wireless communication network, access point equipment, terminal equipment and wireless network controller
CN109391934B (en) Data reporting method and mobile terminal
CN107241262B (en) Data receiving, sending and transmitting method, sending end, receiving end and server
CN111465119A (en) Data sending method, information configuration method, terminal and network equipment
CN111949133B (en) Haptic feedback method, related device and computer-readable storage medium
WO2018107603A1 (en) Method and terminal for connecting to access point
EP3606150A1 (en) Data transmission method, sending-end device and receiving-end device
EP2978190B1 (en) Causing rendering of information indicative of apparatus identification information

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
GR01 Patent grant
GR01 Patent grant