WO2022165447A2 - Methods and apparatus for communications over data radio bearer - Google Patents

Methods and apparatus for communications over data radio bearer Download PDF

Info

Publication number
WO2022165447A2
WO2022165447A2 PCT/US2022/032232 US2022032232W WO2022165447A2 WO 2022165447 A2 WO2022165447 A2 WO 2022165447A2 US 2022032232 W US2022032232 W US 2022032232W WO 2022165447 A2 WO2022165447 A2 WO 2022165447A2
Authority
WO
WIPO (PCT)
Prior art keywords
drb
qos flow
data
packet
qos
Prior art date
Application number
PCT/US2022/032232
Other languages
French (fr)
Other versions
WO2022165447A3 (en
Inventor
Hao Bi
Original Assignee
Futurewei Technologies, Inc.
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 Futurewei Technologies, Inc. filed Critical Futurewei Technologies, Inc.
Publication of WO2022165447A2 publication Critical patent/WO2022165447A2/en
Publication of WO2022165447A3 publication Critical patent/WO2022165447A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the present disclosure relates generally to methods and apparatus for wireless communications, and, in particular embodiments, to methods and apparatus for communications of over data radio bearer.
  • DRB Data radio bearer
  • a method includes: determining, by a communication device, a characteristic measure of a first data radio bearer (DRB); and when the characteristic measure of the first DRB satisfies a condition, mapping, by the communication device, a first data packet of a quality of service (QoS) flow to the first DRB; and transmitting, by the communication device, the first data packet over the first DRB.
  • DRB data radio bearer
  • the method further includes: when the characteristic measure of the first DRB does not satisfy the condition, determining, by the communication device, whether to map the data packet of the QoS flow to a second DRB for transmission.
  • the method further includes: determining, by the communication device, a characteristic measure of the second DRB.
  • the method further includes: determining, by the communication device, that a characteristic measure of a third DRB satisfies the condition; mapping, by the communication device, a second data packet of the QoS flow to the third DRB; and transmitting, by the communication device, the second data packet over the third DRB.
  • the characteristic measure of the first DRB, the second DRB or the third DRB comprises one of following: a data volume in a queue of a DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or a priority of the DRB.
  • MDBV maximum data burst volume
  • the method further includes: comparing, by the communication device, the characteristic measure of the first DRB with a threshold to determine whether the characteristic measure of the first DRB satisfies the condition.
  • the condition specifies the characteristic measure of the first DRB and the threshold.
  • the characteristic measure of the first DRB comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition.
  • the characteristic measure of the first DRB is a sum or an average of values of the characteristic measure of the first DRB for a period of time.
  • the communication device is a user equipment (UE).
  • the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
  • RRC radio resource control
  • a method includes: determining, by a communication device, a characteristic measure of data packets of a quality of service (QoS) flow; when the characteristic measure of the data packets satisfies a condition, mapping, by the communication device, a first data packet of the QoS flow to a first data radio bearer (DRB); and transmitting, by the communication device, the first data packet over the first DRB.
  • QoS quality of service
  • the method further includes: when the characteristic measure of the data packets does not satisfy the condition, mapping, by the communication device, the first data packet of the QoS flow to a second DRB; and transmitting, by the communication device, the first data packet over the second DRB.
  • the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
  • MDBV maximum data burst volume
  • the method further includes: comparing, by the communication device, the characteristic measure of the data packets of the QoS flow with a threshold to determine whether the characteristic measure satisfies the condition.
  • the condition specifies the characteristic measure and the threshold.
  • the characteristic measure comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition.
  • the characteristic measure is a sum or an average of values of the characteristic measure of the packets of the QoS flow for a period of time.
  • the communication device is a user equipment (UE).
  • UE user equipment
  • the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
  • RRC radio resource control
  • a method includes: determining, by a communication device, a characteristic measure of a data radio bearers (DRB) or of packets of a quality of service (QoS) flow; when the characteristic measure satisfies a condition, generating, by the communication device, a report of transmission characteristics of one or more data packets of the QoS flow.
  • DRB data radio bearers
  • QoS quality of service
  • the characteristic measure of the DRB comprises one of following: a data volume in a queue of the DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or a priority of the DRB.
  • MDBV maximum data burst volume
  • the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
  • MDBV maximum data burst volume
  • the method further includes: comparing, by the communication device, the characteristic measure with a threshold to determine whether the characteristic measure satisfies the condition.
  • the condition specifies the characteristic measure of the first DRB and the threshold.
  • the report comprises one or more of following: a data rate; a transmission delay; a packet waiting time; a queue size; data transmitted in a time window; number of packet errors in a time duration; time taken for successful packet transmission; or a packet dropping rate.
  • the communication device is a user equipment (UE).
  • UE user equipment
  • the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for generating the report, the configuration comprising the condition.
  • RRC radio resource control
  • an apparatus includes a non-transitoiy memory storage comprising instructions; and one or more processors in communication with the memoiy storage, wherein the instructions, when executed by the one or more processors, cause the apparatus to perform a method in any of the preceding aspects.
  • a non-transitoiy computer-readable media stores computer instructions that when executed by one or more processors of an apparatus, cause the apparatus to perform a method in any of the preceding aspects.
  • An advantage of the aspects of the present disclosure is that QoS flow to DRB mapping adapts to traffic burst and fast changing radio interface conditions. This helps support low latency high throughput communication.
  • the aspects of the present disclosure allow resources configured for a DRB to be allocated according to the instantaneous need of a QoS flow and/or DRB statuses, and enable a more efficient resource allocation in a communication system.
  • Figure 1 is a diagram of an example communications system
  • FIG. 2 is a diagram of an example mapping of data packets to data radio bearers (DRBs) in a conventional manner
  • Figure 3 is a flow diagram of operations occurring in a prior art technique for mapping data packets to DRBs;
  • Figure 4 is a flow diagram of example operations occurring in matching packets of QoS flows to DRBs based on a characteristic measure according to example embodiments presented herein;
  • Figure 5 is a flow diagram of example operations occurring in mapping packets of a QoS flow to a DRB based on a queue size of the DRB according to example embodiments presented herein;
  • Figure 6 is a flow diagram of example operations occurring in mapping packets of a QoS flow to a DRB based on a cumulative characteristic measure according to example embodiments presented herein;
  • Figure 7 is a flow diagram of example operations occurring in configuring and mapping of QoS flows to DRBs based on a characteristic measure according to example embodiments presented herein;
  • Figure 8 is a flow diagram of example operations occurring in reporting connection conditions of QoS flows to applications according to example embodiments presented herein;
  • Figure 9 is an overview diagram of layers and sublayers involved in mapping of packets of QoS flows of applications to DRBs according to example embodiments presented herein;
  • Figure 10 is a flow diagram of example operations occurring in reporting connection conditions of QoS flows to applications according to example embodiments presented herein;
  • Figure 11 is a flow diagram of example operations occurring in configuring and reporting connection statuses of QoS flows to applications according to example embodiments presented herein;
  • Figure 12 is a flow diagram of example operations occurring in mapping QoS flows to DRBs based on characteristic measures of DRBs according to example embodiments presented herein;
  • Figure 13 is a flow diagram of example operations occurring in mapping QoS flows to DRBs based on characteristic measures of the QoS flows according to example embodiments presented herein;
  • Figure 14 is a flow diagram of example operations occurring in reporting connection status of a QoS flow
  • Figure 15 illustrates an example communication system according to example embodiments presented herein;
  • Figures 16A and 16B illustrate example devices that may implement the methods and teachings according to this disclosure;
  • Figure 17 is a block diagram of a computing system that may be used for implementing the devices and methods disclosed herein.
  • QoS quality of service
  • DRBs data radio bearers
  • Embodiments of the present disclosure provide methods and apparatus for dynamic mappings of QoS flows to DRBs.
  • a user equipment may map packets of a QoS flow to DRBs based on characteristic measures of the DRBs and/ or characteristic measure of packets of the QoS flow.
  • the UE may map a data packet of the QoS flow to the DRB.
  • the UE may map a data packet of the QoS flow to a DRB.
  • the UE may then transmit the data packet over the mapped DRB.
  • the UE may further generate a report of transmission characteristics of one or more data packets of the QoS flow when the characteristic measure satisfies a reporting condition. The report may be used by applications of the UE in generating and processing packets to be transmitted.
  • Figure 1 illustrates an example communications system too.
  • Communications system too includes an access node 105 serving user equipments (UEs), such as UEs no, 112, 114, 116, and 118.
  • Access node 105 is connected to a backhaul network that provides connectivity to services and the Internet.
  • UEs user equipments
  • In a first operating mode communications to and from a UE passes through access node 105.
  • In a second operating mode communications to and from a UE do not pass through access node 105, however, access node 105 typically allocates resources used by the UE to communicate when specific conditions are met. Communication between a UE pair in the second operating mode occurs over sidelinks, comprising uni-directional communication links.
  • Communication between a UE and access node pair also occur over uni-directional communication links, where the communication links from the UE and to access node are referred to as uplinks, and the communication links from the access node to the UE is referred to as downlinks.
  • Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master or primaiy eNBs (MeNBs), secondary eNBs (SeNBs), master primaiy gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on.
  • UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like.
  • Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE- A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na/b/g/n/ac/ad/ax/ay/be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and five UEs are illustrated in Figure 1 for simplicity.
  • 3GPP Third Generation Partnership Project
  • LTE long term evolution
  • LTE- A LTE advanced
  • 5G LTE 5G LTE
  • 5G NR sixth generation
  • HSPA High Speed Packet Access
  • 802.11 family of standards such as 802.na/b/g/n/ac/ad/ax/ay/be, etc. While it is understood that communications
  • a communication device e.g., a UE or an AN
  • the data packets may be mapped into different flows (also referred to as packet flows or data flows), e.g., quality of service (QoS) flows, according to some rules.
  • QoS quality of service
  • packets having a common characteristics, property or QoS requirement may be mapped into one flow.
  • QoS flows will be used as an example for illustration purpose only, and other packet flows may also be applicable.
  • a QoS flow may include a stream of data packets that have one or more common QoS requirements.
  • the QoS flows may then be mapped to data radio bearer (DRBs), and transmitted over the mapped DRBs.
  • DRBs data radio bearer
  • a bearer is a logical or virtual concept, and may be understood as a carrier or a link between a transmitting point and a receiving point.
  • a bearer defines how data/signaling is treated when it travels across a network.
  • a DRB is configured to cany user-plane traffic, e.g., user data, internet protocol packets, and so on.
  • Some related 3GPP standards have provided specifications about mapping QoS flows to DRBs. The standards may continue to evolve.
  • Figure 2 illustrates a diagram 200 of an example mapping of data packets to DRBs in a conventional manner.
  • the mapping of data packets to DRBs may occur over multiple layers, including an application layer 205, a non-access stratum (NAS) layer 207, and an access stratum (AS) layer 209.
  • application layer 205 data packets (such as data packets 210, 211, and 212) are generated by an application.
  • NAS layer 207 NAS QoS rules 215 map the data packets to QoS flows, such as a QoS flow 217.
  • QoS flow identifiers QoS flow identifiers (QFIs) are applied to packets of the respective QoS flows in NAS layer 207, where packets of a single QoS flow have the same QFI.
  • the QoS flows in this layer may be segregated into Internet Protocol (IP) flows 218 or non-IP flows 219, for example.
  • IP Internet Protocol
  • AS rules 220 map the QoS flows to DRBs. As an example, packets with a certain QFI are mapped to a particular DRB.
  • Figure 3 illustrates a flow diagram of operations 300 occurring in a prior art technique for mapping data packets to DRBs.
  • the mapping of the data packets includes mapping the data packets to QoS flows (block 305).
  • the mapping of the data packets to QoS flows occurs in the NAS layer and utilizes NAS QoS rules. Some example mappings may be found in 3GPP related standards.
  • a QFI is also applied to the packets of each QoS flow.
  • the packets of the QoS flows are mapped to DRBs (block 307).
  • the mapping of packets of the QoS flows to DRBs is performed in the AS layer. As an example, packets of one QoS flow are mapped to one DRB. As another example, multiple QoS flow may be mapped to one DRB.
  • the mapping of the data packets to QoS flows may be based on certain QoS rules, so that packets in a QoS flow share certain common characteristics, e.g., certain requirements on data rate, delay, or reliability.
  • UEs are configured with QoS flow to DRB mapping rules in a semi-static fashion. That is, mapping of QoS flows to DRBs follows the semi-statically configured mapping rules, and is not capable of dynamically adjusting mapping of QoS flows to DRBs. Thus, dynamic mapping between QoS flows and DRBs is not provided, e.g., based on characteristic of the DRBs and/or packets of the QoS flows.
  • the maximum data burst volume is the largest amount of data that a 5G access network (5G-AN) is required to serve within a period of a 5G-AN packet delay budget (PDB).
  • PDB packet delay budget
  • GBR guaranteed bit rate
  • PER packet error rate
  • Each GBR QoS flow may be associated with an averaging window.
  • the averaging window represents the duration over which the GFBR and the maximum flow bit rate (MFBR) are calculated (e.g., in a radio access network (RAN), AN, user plane function (UPF), UE, etc.).
  • RAN radio access network
  • UPF user plane function
  • Table 1 below presents default priority levels, PDB, PER, averaging window size, and example services for different 5G QoS identifier (5QI) parameter values, according to 3GPP TS 23.501 "System architecture for the 5G System (5GS)," which is herein incorporated by reference.
  • Table 1 Example default priority levels, PDB, PER, averaging window size, and example services for different 5G QoS identifier (5QI) parameter values
  • successful transmission of a QoS flow depends on mapping of packets of the QoS flow to appropriate DRBs, packet delay budget, PER, and other factors. It is thus desirable to dynamically map QoS flows to DRBs that meet specific requirements of different QoS flows.
  • Embodiments of the present disclosure provide methods and apparatus for dynamic mappings of QoS flows to DRBs.
  • the dynamic mappings may be based on characteristic measures of the DRBs and/or the QoS flows, such as data rate, reliability, delay, and/or any other metrics of the DRBs and/or the QoS flows.
  • a characteristic measure may be a running sum (or summation), or average, or a result of any other applicable processing, of metrics (such as MDBV, data rate, packet error rate, delay, data volume in a queue, packet waiting time, data transmitted in a time interval, time taken for successful transmission, any other QoS metrics, etc.) over a time duration.
  • a characteristic measure may also be a combination of multiple different characteristic metrics.
  • one or more characteristic measure of a DRB and/or a QoS flow may be assessed against one or more conditions, and when the one or more conditions are satisfied, one or more packets of the QoS flow may be mapped to the DRB and transmitted over the mapped DRB.
  • one of a plurality of DRBs may be selected and packets of the QoS flow are mapped to the selected DRB.
  • Embodiments of the present disclosure have advantage of being able to dynamically map data packets of a QoS flow to DRBs. Dynamic QoS packets to DRBs can match resources configured for a DRB according to the instantaneous need of a QoS flow and DRB status, enabling a more efficient resource allocation in a communication system.
  • a characteristic measure of a DRB may include one or more of following:
  • a data volume in a queue of the DRB (also referred to as a queue size), which may be an amount of data in the queue to be transmitted over the DRB;
  • a data rate of the DRB which may be an amount of data transmitted in a unit time
  • MDBV maximum data burst volume
  • a transmission delay of the DRB which may be the average time of successful transmission of packets in a DRB during a measuring period. It may include waiting time and time taken for successful transmission;
  • a characteristic measure of packets of a QoS flow may include one or more of following:
  • a data rate of the QoS flow which may be an amount of data of the QoS flow arriving for transmission in a unit time
  • MDBV maximum data burst volume
  • a data volume of the QoS flow which may be an amount of data of the QoS flow in a buffer at a certain measurement time
  • a packet size of a packet of the QoS flow which may be a size of a packet, or an average size of packets
  • a packet type of a packet of the QoS flow e.g., IP, non-IP, video, voice, encoded, un-encoded packets, and so on, which may depend on applications;
  • packet waiting time of the QoS flow which may be a time period that a packet of the QoS flows waits for being transmitted, e.g., a time period from arrival of the packet of the QoS flow to transmission of the packet;
  • a buffer size of the QoS flow which may be a size of a buffer buffering packets of the QoS flow.
  • the “characteristic measure of packets of a QoS flow” may also be referred to as “characteristic measure of a QoS flow” in embodiments of the present.
  • a characteristic measure of a QoS flow may be related to a packet of the QoS flow, multiple packets of the QoS flow, or the entire QoS flow.
  • the dynamic QoS flows to DRBs mapping operations may be configured using signaling, such as radio resource control (RRC) signaling.
  • RRC radio resource control
  • a UE may receive a QoS flow to DRB mapping configuration (or rule) in RRC signaling.
  • the UE may perform QoS flow to DRB mapping according to the received configuration.
  • the UE may be configured to switch dynamically the QoS flow to DRB mapping according to another configuration.
  • the QoS flow to DRB mapping configuration/rule may specify one or more conditions for mapping QoS flows to DRBs.
  • the condition may include information or criterion for determining which packet(s) of a QoS flow is to be mapped to which DRB.
  • An example condition may include information about one or more characteristic measures to be taken (or used), and one or more thresholds of the characteristic measures to be used for determining which DRB packets of a QoS flow are to be mapped to.
  • a condition may specify:
  • next DRB will be assessed similarly to DRB1 using the same threshold or a different threshold.
  • the next DRB e.g., DRB2
  • the packet is mapped to DRB2; however, if the data rate of DRB2 is not greater than the threshold, a next DRB, e.g., DRB3, may then be assessed similarly, until a DRB satisfying the condition is found.
  • the DRBs being assessed may be pre-determined. When no DRB is found to satisfy the condition, the packet may be mapped to a default DRB for transmission.
  • This example maps the QoS flow to DRBs based on a characteristic measure of the DRBs, i.e., a data rate of the DRBs.
  • a characteristic measure of the DRBs i.e., a data rate of the DRBs.
  • Other characteristic measures of the DRBs may be used similarly.
  • a condition may specify:
  • a DRB may be selected from a plurality of DRBs based on whether a condition is satisfied by the DRB, and a packet of a QoS flow is mapped to the selected DRB.
  • a condition may specify:
  • packet waiting time of each of a plurality of DRBs may be obtained and compared with the threshold time, and one DRB satisfying the condition may be selected for transmitting a packet of a QoS flow.
  • different thresholds may be configured for different DRBs in a condition. For example, if a first DRB has a large buffer and a second DRB has a small buffer, a queue size threshold for the first DRB may be larger than the queue size threshold for the second DRB.
  • a condition may specify:
  • the above example maps packets of a QoS flow to DRBs based on a characteristic measure of a QoS flow, i.e., a packet size of a packet of the QoS flow.
  • a characteristic measure of a QoS flow i.e., a packet size of a packet of the QoS flow.
  • Other characteristic measures of the packets of the QoS flow may be used similarly.
  • a condition may specify:
  • packets of a QoS flow may be mapped to DRBs based on a characteristic measure of the DRBs and a characteristic measure of packets of the QoS flow.
  • a condition may specify:
  • a service data application protocol (SDAP) entity may perform dynamic mapping of QoS flows to multiple DRBs for packets of a QoS flow, based on one or more configured mapping conditions.
  • SDAP service data application protocol
  • An SDAP protocol data unit is generated for an SDAP service data unit (SDU) from an upper layer for a QoS flow;
  • the SDAP entity will map the SDAP PDU to the DRB.
  • Figure 4 illustrates a flow diagram of example operations 400 occurring in dynamic mapping of packets of QoS flows to DRBs based on a characteristic measure of DRBs and/or the QoS flow.
  • Operations 400 may be indicative of operations occurring in a device, such as a UE, as the device dynamically maps packets of a QoS flow to DRBs based on a characteristic measure.
  • Operations 400 begin with the UE receiving configuration of QoS flow to DRB mappings (block 405).
  • the configuration of QoS flow to DRB mappings may be received in RRC signaling from an access node serving the UE, for example.
  • a QoS flow packets of the QoS flow
  • the UE maps data packets to QoS flows (block 407).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the UE maps the QoS flows to DRBs (block 409).
  • the mapping of the QoS flows to DRBs may include the UE comparing a characteristic measure of a DRB or a QoS flow to a threshold, where the threshold may differ among different DRBs. As an example, if a first DRB has a large buffer and a second DRB has a small buffer, the queue size threshold for first DRB may be larger than the queue size threshold for the second DRB.
  • Figure 5 illustrates a flow diagram of example operations 500 occurring in dynamic mapping of packets of a QoS flow to a DRB based on a DRB queue size.
  • Operations 500 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of a QoS flow to a DRB with dynamic switching based on DRB queue size.
  • Operations 500 begin with the device mapping data packets to QoS flows (block 505).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the device determines the current queue size of a DRB (block 507).
  • the device may determine the queue status of the DRB based on the buffered data at medium access control/radio link control/packet data convergence protocol (MAC/RLC/PDCP) entities associated with the DRB. Alternatively, the device may sum the buffer status of logic channels associated with the DRB.
  • MAC/RLC/PDCP medium access control/radio link control/packet data convergence protocol
  • the device performs a check to determine if the queue size of the DRB meets a specified threshold (block 509).
  • the specified threshold may be specified in the configuration of QoS flow to DRB mappings, for example. In an embodiment, the specified threshold may be based on the maximum queue size allowed for the DRB. In an embodiment, the specified threshold may be based on the maximum delay that a packet of a QoS flow can tolerate.
  • the specified threshold may specify a cumulative data volume or time spent within data buffers of the MAC/RLC/PDCP entities of the DRB.
  • the device maps one or more packets of a QoS flow to the DRB (block 511). In other words, if the data stored in the queue of the DRB is less than the specified threshold, the device may deliver more data to the DRB.
  • the device transmits packets of the QoS flow over the mapped DRB (e.g., a first DRB) (block 513).
  • the device does not map the packets of the QoS flow to the DRB. Instead, the packets of the QoS flow may either be buffered at the SDAP entity or mapped to another DRB (e.g., a second DRB) (block 515).
  • a second DRB e.g., a second DRB
  • mapping the packets of the QoS flow to the first DRB would increase the buffering in the first DRB to an undesirable level, and data mapped to the DRB in the future would thus experience longer transmission delay.
  • the packets of the QoS flow may be mapped to another DRB (e.g., the second DRB), if the second DRB does not have a configured queue size threshold, or the threshold is met by the second DRB.
  • the packets of the QoS flow may be stored in the SDAP entity temporarily and wait to be transmitted over the first DRB.
  • the queue size is merely a single example of a characteristic measure of the DRB.
  • the example embodiments are operable with other characteristic measures, which may include data rate, latency, reliability, data transmitted in a time interval, number of dropped packet in a time duration, buffering time, or any other QoS metrics as described previously.
  • Figure 6 illustrates a flow diagram of example operations 600 occurring in mapping packets of a QoS flow to a DRB based on a cumulative characteristic measure of the QoS flow.
  • Operations 600 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of the QoS flow to one or more DRBs based on the cumulative characteristic measure.
  • Operations 600 begin with the device mapping data packets to QoS flows (block 605).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the device determines the cumulative characteristic measure of the QoS flow (block 607).
  • the characteristic measure may be one or more of MDBV, data rate, latency, delay, packet error, dropped packet, any other QoS metrics, etc., as described above.
  • the cumulative characteristic measure may be a combination of multiple metrics of the QoS flow.
  • the cumulative characteristic measure may include a data rate of the QoS flow and a packet size of the QoS flow.
  • the cumulative characteristic measure may be a cumulative measure of a characteristic of the QoS flow during a period of time or for a number of packets of the QoS flow.
  • the characteristic measure is a data rate
  • the cumulative characteristic measure may be a cumulative data rate, which may be defined as a sum of data rates of the QoS flow during a period of time.
  • the characteristic measure is an amount of data transmitted in a time duration
  • the cumulative characteristic measure may be cumulative data transmitted during a period of time, which may be defined as a sum of transmitted data during the period of time.
  • the cumulative characteristic measure may be a cumulative packet size, which may be defined as an average packet size of some or all packets of the QoS flow.
  • Other cumulative characteristic measures may be similarly defined.
  • the device performs a check to determine if the cumulative characteristic measure of the QoS flow meets a specified threshold (block 609).
  • the specified threshold may be specified in the configuration of QoS flow to DRB mappings, for example.
  • the specified threshold may be based on the characteristic measure to be used, e.g., the maximum sum of data rates of the QoS flow, or the maximum sum of transmitted data of the QoS flow in a time duration.
  • the device maps a packet of the QoS flow to a first DRB (block 611).
  • the device transmits the packet of the QoS flow over the mapped DRB (e.g., the first DRB) (block 617).
  • the device may either buffer one or more packets of the QoS flow at an SDAP entity of the first DRB, or map one or more packets of the QoS flow to a second DRB, e.g., a DRB configured with default or backup characteristic parameters (block 615).
  • the device transmits a packet of the QoS flow over the mapped DRB (e.g., the second DRB) (block 617).
  • packets of the QoS flow may be temporarily buffered in the SDAP entity, i.e., not delivered to DRBs immediately, if the cumulative characteristic measure of the QoS flow does not meet or exceeds the specified threshold indicative of what is required by the QoS flow.
  • the threshold, the first DRB and the second DRB may be specified as a condition in a configuration of QoS flow to DRB mappings.
  • a condition may specify:
  • a condition may specify:
  • Figure 6 illustrates a method for mapping packets of a QoS flow to DRBs based on a cumulative characteristic measure of the QoS flow
  • Figure 6 illustrates a method for mapping packets of a QoS flow to DRBs based on a cumulative characteristic measure of DRBs, or based on cumulative characteristic measures of the QoS flow and DRBs.
  • Figure 7 illustrates a flow diagram of example operations 700 occurring in configuring and dynamic mapping of QoS flows to DRBs based on a characteristic measure of QoS flows.
  • Operations 700 may be indicative of operations occurring in a device, such as a UE, as the device configures and maps the QoS flow to DRBs based on a characteristic measure of the QoS flow.
  • Operations 700 begin with the device receiving a configuration of QoS flow to DRB mappings (block 705).
  • the configuration of QoS flow to DRB mappings may be received in RRC signaling.
  • the RRC signaling may be received from an access node serving the UE.
  • the QoS flow may be mapped to two or more DRBs based on characteristic measures of packets of the QoS flow. Examples of characteristic measures include MDBV, a data rate, a data volume, a packet size, a packet type, packet waiting time, a data buffer size (for a QoS flow), priority of a QoS flow, or any other QoS metrics, etc. as described above.
  • the UE maps data packets to QoS flows (block 707).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the UE determines the characteristic measure of packets of the QoS flow (block 709).
  • the characteristic measure may be determined by measuring the QoS flow (or packets of the QoS flow) over an averaging window, or checking the size or type of packets of the QoS flow, for example.
  • the UE maps the QoS flow to a DRB in accordance with the characteristic measure of the QoS flow (block 711).
  • the UE compares the characteristic measure of the QoS flow with a threshold and maps the QoS flow to one of the DRBs in accordance with the result of the comparison.
  • the UE transmits a packet of the QoS flow over the mapped DRB (block 713).
  • the characteristic measure of the QoS flow may be a packet size. A packet may be mapped to one DRB, if its size is below the threshold, and the packet may be mapped to another DRB, if its size is equal to or larger than the threshold.
  • the characteristic measure of the QoS flow may be packet waiting time.
  • a packet may be mapped to one DRB, if its waiting time is below the threshold, and the packet may be mapped to another DRB, if its waiting time is equal to or larger than the threshold.
  • the threshold may be pre-defined per DRB, or generally for multiple DRBs to which the QoS flow is to be mapped.
  • comparisons may be possible. As an example, rather than determining if a characteristic measure is equal to or exceeds a specified threshold, the comparison may determine whether the characteristic measure is below the specified threshold. The comparison may also be reversed, such as the comparison determines whether the characteristic is larger than the specified threshold, etc.
  • One or more QoS flows may be mapped to a same DRB. Separate priorities may be configured to QoS flows for their mapping to the DRB. When packets of the QoS flows are mapped to a DRB, packets of the QoS flow with higher priority may be mapped to the DRB first, and packets of the QoS flow with lower priority may be mapped to the DRB afterwards.
  • a volume threshold may be configured for a QoS flow together with the priority for mapping. The volume threshold may be the maximum amount of data, e.g., the number of bytes of the data or the number of packets of the QoS flow, that can be mapped to a DRB when it is the turn of the QoS flow to perform mapping according to the priority.
  • the volume threshold may be subject to the restriction of maximum queue size of the DRB. That is, the maximum amount of data of a QoS flow mapped to a DRB should make the queue of the DRB exceed the maximum queue size of the DRB for the QoS flow.
  • Adaptive streaming applications adjust the speed needed to stream media content, such as audio and video, according to different connection conditions. For example, streaming may be done at a higher data rate with better resolution when connection is good. On the other hand, streaming speed may be reduced when connection deteriorates with more congestion and longer delay.
  • Packets from applications are served as Quality of Service (QoS) flows in a 5G system. As described above, packets generated by application(s) are mapped to QoS flows, and the QoS flows are mapped to DRBs.
  • QoS Quality of Service
  • a DRB defines the packet treatment (i.e., how a packet is transmitted, e.g., how fast, or how reliable the packet is to be transmitted) on a radio interface (e.g., between a transmitting device and a receiving device/ network).
  • a DRB serves packets with the same packet forwarding treatment.
  • QoS flows are transmitted using DRBs over the radio interface.
  • connection conditions/ statuses of the radio interface such as data rate, delay, packet error rate, etc., need to be exposed to the applications.
  • An application may adjust its packet generation, e.g., a packet generation rate, based on the connection conditions/statuses of the radio interface, in order to adaptively streaming data packets.
  • connection condition connection status
  • transmission condition transmission status
  • transmission status transmission status
  • connection condition/statuses of the radio interface may be represented or indicated by characteristic measures of DRBs over which QoS flows are transmitted, or by characteristic measures of packets of QoS flows.
  • a connection condition/status may be determined and reported specifically for packets, for one or more QoS flows, or for one or more DRBs, based on characteristic measures of DRBs or QoS flows.
  • the characteristic measures of the DRBs or the QoS flows may include one or more characteristic measures of DRBs or QoS flows as described above, and/or any other measures related to packet transmissions.
  • transmission characteristics are also referred to as transmission characteristics, connection characteristics, or transmission statistics, in the following description, as they reflect the connection statuses of the air interface.
  • the transmission characteristics may be measured and reported to one or more applications, and used by the one or more applications in generating or outputting data packets.
  • methods and apparatus are provided for updating transmission characteristics to applications.
  • the updating of the transmission characteristics may be performed dynamically, and performed by reporting the transmission characteristics to the applications.
  • the dynamic updates may be based on one or more characteristic measures of DRBs and/or QoS flows, such as data rate, reliability, delay, queue size, time taken to successfully transmit packets, data transmitted in a time interval, number of dropped packets, number of packet errors, any QoS metrics, etc.
  • a characteristic measure may be a running sum (or summation), or average, or a result of any processing, of a characteristic metric (such as data rate, packet error rate, delay, queue size, data transmitted in a time interval, number of dropped packets, number of packet errors, any other QoS metrics, etc.) over a time duration, and/or a combination of multiple different characteristic metrics.
  • a characteristic metric such as data rate, packet error rate, delay, queue size, data transmitted in a time interval, number of dropped packets, number of packet errors, any other QoS metrics, etc.
  • one or more transmission characteristics of DRBs or QoS flows may be measured, and one or more reports may be generated and reported to one or more applications, when a reporting condition or criterion (reporting trigger condition/criterion) is satisfied.
  • a reporting condition or criterion reporting trigger condition/criterion
  • one or a plurality of reports may be made to selected applications.
  • one or a plurality of reports may be made periodically to applications according to configured time intervals.
  • a report may include one or more characteristic measures of one or more QoS flows or one or more DRBs.
  • the reported characteristic measures reflect a connection or transmission status of a QoS flow.
  • the report enables an application to update the connection or transmission status of the QoS flow, i.e., transmission characteristics/ statistics of data packets, based on which the application may adjust its packet generation.
  • the reporting of transmission characteristics for QoS flows and/or DRBs to applications may be configured using signaling, such as radio resource control (RRC) signaling.
  • RRC radio resource control
  • other types of signaling are possible.
  • reporting of transmission status of QoS flows to applications is configured using RRC signaling.
  • the configuration also specifies a reporting trigger condition, such as characteristic measures, as well as thresholds corresponding to one or more characteristic measures used in the comparison of the characteristic measures.
  • a service data application protocol (SDAP) entity may perform status update of QoS flows to applications, based on a queue size of a DRB.
  • SDAP service data application protocol
  • the SDAP entity reports transmission characteristics of QoS flows transmitted over the DRB to applications.
  • An embodiment method may include collecting transmission characteristics of DRBs carrying packets of QoS flows, and determining a connection condition for a QoS flow.
  • transmission characteristics may be measured on data volume in a queue of a DRB.
  • a queue size may be measured as the data volume in MAC/RLC/PDCP entities of a DRB, and it may be equivalent to the sum of buffer status of logical channels associated with the DRB.
  • Transmission characteristics may also be measured on a data volume transmitted in a time duration, a packet error rate of the transmission, the time taken for packets to be successfully transmitted, the number of dropped packets, the time for packets to be mapped from a QoS flow to one or more DRBs, etc.
  • Connection condition of a QoS flow may be determined based on transmission characteristics of data radio bearers. Connection condition of a QoS flow may be measures of data rate, transmission delay, packet error rate, data volume in a time window, average queue size, etc. This helps support low latency high throughput communication.
  • Figure 8 illustrates a flow diagram of example operations 800 occurring in dynamic update of transmission status of QoS flows to applications based on a characteristic measure.
  • Operations 800 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of QoS flows to DRBs.
  • Operations 800 begin with the UE receiving a configuration of QoS flow to DRB mappings (block 805).
  • the configuration of QoS flow to DRB mappings maybe received in RRC signaling from an access node serving the UE, for example.
  • a QoS flow may be mapped to two or more DRBs, where a particular QoS flow to DRB mapping is based on a characteristic measure of the DRBs as described above. Examples of characteristic measures include data rate, priority, reliability, queue size, delay, data transmitted in a time interval, number of dropped packets, number of packet errors, any other QoS metrics, etc.
  • the UE maps data packets to QoS flows (block 807).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the UE maps the QoS flows to DRBs (block 909).
  • the mapping of the QoS flows to DRBs may include the UE comparing a characteristic measure of a DRB or a QoS flow to a threshold, where the threshold may differ among different DRBs, for example.
  • the UE generates reports of connection status of QoS flows (block 811).
  • the report of connection status of QoS flows may include one or more characteristic measures of QoS flows or DRBs, such as data rate, reliability, delay, data volume in a time interval, number of packet errors in a time interval, queue size, number of dropped packets, any other QoS metrics, etc.
  • Ttrigger events of generating reports of transmission statistics may include the UE comparing characteristic measures of DRBs or QoS flows to a threshold, where the threshold may differ between different QoS flows or DRBs.
  • the updates of transmission statistics of QoS flows may also be done periodically at specified time intervals. Event triggering and periodic reporting can be configured together for update of connection status reporting to applications.
  • Conditions (or events) for triggering reporting of connection statuses of QoS flows may be configured based on characteristic measures of QoS flows and/or DRBs.
  • Example trigger conditions/events may include:
  • the above example trigger conditions are merely provided for illustration purposes. Those of ordinaiy skill in the art would recognize that many variations, alternatives and embodiments may be applicable for configuring the reporting trigger conditions by use of characteristic measures of DRBs and/ or QoS flows. A criterion may be satisfied when a characteristic measure is greater than a threshold, less than a threshold, equal to a threshold, within a threshold range, or an applicable combination thereof. As described above, the characteristic measure may be a cumulative characteristic measure.
  • FIG. 9 is a diagram 900 of overview of sublayers involved in mapping of packets of QoS flows of applications to DRBs.
  • application data/packets of different data rates e.g., high data rate, median data rate, and low data rate
  • the application data/packets are mapped to different QoS flows in the SDAP sublayer.
  • the QoS flows are mapped to DRBs in the PDCP/RLC/MAC sublayers for transmission according to uplink (UL) grant and logical channel prioritization (LCP), for example.
  • the UL grant indicates scheduled time and radio resources for uplink transmissions.
  • the LCP indicates how transmission resources are allocated among different DRBs.
  • Feedback data i.e., transmission characteristic measures
  • data rate and queue size information may be measured and fed back from the PDCP/RLC/MAC sublayers to the SDAP sublayer.
  • Data rate and latency (e.g., packet transmission delay) information may be generated by the SDAP sublayer based on the data rate and queue size information, and fed back from the SDAP sublayer to the application layer.
  • the information about the data rate and latency information may be specifically for one or more QoS flows related to the applications.
  • the data rate and queue size information may be measured based on characteristic measures of one or more DRBs and/ or one or more QoS flows.
  • Figure 10 illustrates example operations 1000 occurring in exposing QoS flows’ connection status information of data rate and latency to an application based on measures of DRB queue sizes and data rates. Other characteristic measure may also be used.
  • Operations 1000 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of QoS flows (serving application data) to DRBs.
  • Operations 900 may occur in the layers and sublayers as shown in Figure 9.
  • Operations 1000 begin with the SDAP entity of the device receiving feedback measures of characteristics of DRBs, i.e., data rates and queue sizes of the DRBs, e.g., from the MAC (or RLC, or PDCP) entity of the device, and generating connection status information (block 1005).
  • the MAC (or RLC, or PDCP) entity feeds back characteristic measures of the DRBs, i.e., measures of the data rates and queue sizes, to the SDAP entity, and the SDAP entity generates connection status information of data rate and latency for QoS flows based on the characteristic measures of the DRBs, for example.
  • the connection status information of data rate and latency for QoS flows is fed back to the application layer of the device.
  • the application may generate data packets of one or more of the QoS flows based on the connection status.
  • the mapping of data packets of the application to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the device may map the QoS flow to DRBs using the embodiments described above, e.g., in Figures 5-7.
  • the device determines the current queue size of a DRB (block 1007).
  • the device may determine the queue size of the DRB based on the buffered data at MAC/RLC/PDCP entities associated with the DRB, for example.
  • the device may sum the buffer status of logic channels associated with the DRB.
  • the device performs a check to determine if the queue size of the DRB exceeds a specified threshold (block 1009).
  • the specified threshold may be specified in the configuration of the QoS flows to DRBs mappings, for example.
  • the specified threshold may be based on the maximum queue size allowed for a QoS flow on the DRB. In an embodiment, the specified threshold may be based on the maximum delay a packet of a QoS flow can tolerate.
  • the specified threshold may specify a cumulative data volume within data buffers of MAC/RLC/PDCP entities of the DRB. Alternative comparisons may be possible. As an example, rather than determining if the queue size simply exceeds the specified threshold, the comparison may determine if the queue size is greater than or equal to the specified threshold. The comparison may also be reversed, such as the comparison determines if the queue volume is less than the specified threshold, etc.
  • the device maps the packets of the QoS flow to the DRB (block ton). In other words, if the data stored in the queue of the DRB is less than the specified threshold, the device may deliver more data of the QoS flow to the DRB. And the device transmits packets of the QoS flow over the mapped DRB (e.g., the first DRB) (block 1013).
  • the device If the queue size of the DRB meets or exceeds the specified threshold, the device generates transmission reports of the QoS flow being mapped to the DRB (block 1015). In other words, if the data volume stored in the queue of the first DRB meets (e.g., is equal to or higher than) the specified threshold, mapping packets of the QoS flow over the first DRB may increase the buffering in the first DRB to an undesirable level, so data mapped to the DRB in future may experience longer transmission delay. Hence, connection status information is updated about the data rate and latency in the transmission of packets of the QoS flow.
  • the packets of the QoS flow may be mapped to another DRB, if this DRB does not have a configured queue size threshold, or the threshold has not been met (block 1017). Or alternatively, the packets of the QoS flow may be stored in the SDAP entity temporarily (block 1017).
  • the queue size is a single example of a characteristic measure of the DRB.
  • the example embodiments are operable with other characteristic measures, which may include data rate, latency, packet buffering time, number of packet errors, data transmitted in a time window, time taken for successful transmission, number of dropped packets, any other QoS metrics, etc.
  • Figure 11 illustrates a flow diagram of example operations 1100 occurring in configuring and dynamic reporting of QoS flows’ transmission status on a characteristic measure.
  • Operations 1100 maybe indicative of operations occurring in a device, such as a UE, as the device configures and maps QoS flows to DRBs based on a characteristic measure of the QoS flows or the DRBs.
  • Operations 1100 begin with the device receiving a configuration of QoS flow connection status reporting (block 1105).
  • the configuration of QoS flow connection status reporting may be received in RRC signaling.
  • the RRC signaling may be received from an access node serving the UE.
  • the QoS flow connection status reporting may be triggered based on one or more characteristic measures of packets of QoS flows or packets in DRBs. Examples of characteristic measures include data rate, packet size, packet type, packet waiting time, queue size, data transmitted in a time window, number of packet errors in a time duration, time taken for successful packet transmission, number of dropped packets, any other QoS metrics, etc.
  • the UE maps data packets to QoS flows (block 1107).
  • the mapping of data packets to QoS flows may be in accordance with NAS QoS rules.
  • the packets of a single QoS flow are applied with a QFI associated with the QoS flow.
  • the SDAP entity in the UE determines one or more characteristic measures for a QoS flow connection status report (block 1109).
  • the SDAP entity in the UE generates a status report of QoS flows in accordance with the characteristic measures of packets of the QoS flows (block 1111).
  • the UE compares a characteristic measure with a threshold and updates (i.e., generates and reports) connection status information of a QoS flow if the characteristic measure is equal to or exceeds the threshold.
  • the characteristic measure may be related to the QoS flow, or to one or more DRBs over which packets of the QoS flow are transmitted.
  • connection status reporting may include information of the QoS flow, such as data rate, transmission delay, packet waiting time, queue size, data transmitted in a time window, number of packet errors in a time duration, time taken for successful packet transmission, packet dropping, etc.
  • one connection status report may be generated and reported for one QoS flow, and the reporting trigger condition may be based on one or more characteristic measures related to the QoS or related to one or more DRBs over which packets of the QoS flow are transmitted.
  • FIG. 12 is a flow diagram of example operations 1200 occurring in mapping QoS flows to DRBs based on characteristic measures of DRBs according to example embodiments presented herein.
  • Operations 1200 maybe indicative of operations occurring in a device, such as a UE, as the device maps QoS flows to DRBs based on a characteristic measure of the DRBs.
  • the UE determines a characteristic measure of a first data radio bearer (DRB) (block 1202).
  • DRB data radio bearer
  • QoS quality of service
  • FIG. 13 is a flow diagram of example operations 1300 occurring in mapping QoS flows to DRBs based on characteristic measures of the QoS flows according to example embodiments presented herein.
  • Operations 1300 may be indicative of operations occurring in a device, such as a UE, as the device maps QoS flows to DRBs based on a characteristic measure of the QoS flows.
  • the UE determines a characteristic measure of data packets of a quality of service (QoS) flow (block 1302). When the characteristic measure of the data packets satisfies a condition, the UE maps a first data packet of the QoS flow to a first data radio bearer (DRB), and transmits the first data packet over the first DRB (block 1304).
  • QoS quality of service
  • FIG 14 is a flow diagram of example operations 1400 occurring in reporting connection status of a QoS flow.
  • Operations 1400 may be indicative of operations occurring in a device, such as a UE, as the device reports connection status of a QoS flow.
  • the UE may determine a characteristic measure of a data radio bearers (DRB) or of packets of a quality of service (QoS) flow (block 1402). When the characteristic measure satisfies a condition, the UE generates a report of transmission characteristics of one or more data packets of the QoS flow (block 1404).
  • DRB data radio bearers
  • QoS quality of service
  • Figure 15 illustrates an example communication system 1500.
  • the system 1500 enables multiple wireless or wired users to transmit and receive data and other content.
  • the system 1500 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • NOMA non-orthogonal multiple access
  • the communication system 1500 includes electronic devices (ED) 15103-15100, radio access networks (RANs) I52oa-i52ob, a core network 1530, a public switched telephone network (PSTN) 1540, the Internet 1550, and other networks 1560. While certain numbers of these components or elements are shown in Figure 15, any number of these components or elements may be included in the system 1500.
  • ED electronic devices
  • RANs radio access networks
  • PSTN public switched telephone network
  • the EDs 15103-15100 are configured to operate or communicate in the system 1500.
  • the EDs 15103-15100 are configured to transmit or receive via wireless or wired communication channels.
  • Each ED 15103-15100 represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, or consumer electronics device.
  • UE user equipment or device
  • WTRU wireless transmit or receive unit
  • PDA personal digital assistant
  • smartphone laptop, computer, touchpad, wireless sensor, or consumer electronics device.
  • the RANs I52oa-i52ob here include base stations 1570a- 1570b, respectively. Each base station 1570a- 1570b is configured to wirelessly interface with one or more of the EDs 15103-15100 to enable access to the core network 1530, the PSTN 1540, the Internet 1550, or the other networks 1560.
  • the base stations i570a-i570b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNodeB), a Next Generation (NG) NodeB (gNB), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router.
  • BTS base transceiver station
  • NodeB Node-B
  • eNodeB evolved NodeB
  • NG Next Generation
  • gNB Next Generation NodeB
  • a Home NodeB a Home eNodeB
  • AP access point
  • the EDs 15103-15100 are configured to interface and communicate with the Internet 1550 and may access the core network 1530, the PSTN 1540, or the other networks 1560.
  • the base station 1570a forms part of the RAN 1520a, which may include other base stations, elements, or devices.
  • the base station 1570b forms part of the RAN 1520b, which may include other base stations, elements, or devices.
  • Each base station I57oa-i57ob operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.”
  • MIMO multiple-input multiple-output
  • the base stations 1570a- 1570b communicate with one or more of the EDs 15103-15100 over one or more air interfaces 1590 using wireless communication links.
  • the air interfaces 1590 may utilize any suitable radio access technology.
  • the system 1500 may use multiple channel access functionality, including such schemes as described above.
  • the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B.
  • NR 5G New Radio
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • LTE-B Long Term Evolution-B
  • the RANs I52oa-i52ob are in communication with the core network 1530 to provide the EDs 15103-15100 with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs I52oa-i52ob or the core network 1530 may be in direct or indirect communication with one or more other RANs (not shown).
  • the core network 1530 may also serve as a gateway access for other networks (such as the PSTN 1540, the Internet 1550, and the other networks 1560).
  • some or all of the EDs 15103-15100 may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols.
  • the EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 1550.
  • a service provider or switch not shown
  • the Internet 1550 may be any suitable configuration.
  • Figures 16A and 16B illustrate example devices that may implement the methods and teachings according to this disclosure.
  • Figure 16A illustrates an example ED 1610
  • Figure 16B illustrates an example base station 1670. These components could be used in the system 1500 or in any other suitable system.
  • the ED 1610 includes at least one processing unit 1600.
  • the processing unit 1600 implements various processing operations of the ED 1610.
  • the processing unit 1600 could perform signal coding, data processing, power control, input/output processing, or any other functionality enabling the ED 1610 to operate in the system 1500.
  • the processing unit 1600 also supports the methods and teachings described in more detail above.
  • Each processing unit 1600 includes any suitable processing or computing device configured to perform one or more operations.
  • Each processing unit 1600 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.
  • the ED 1610 also includes at least one transceiver 1602.
  • the transceiver 1602 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 1604.
  • the transceiver 1602 is also configured to demodulate data or other content received by the at least one antenna 1604.
  • Each transceiver 1602 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire.
  • Each antenna 1604 includes any suitable structure for transmitting or receiving wireless or wired signals 1690.
  • One or multiple transceivers 1602 could be used in the ED 1610, and one or multiple antennas 1604 could be used in the ED 1610.
  • a transceiver 1602 could also be implemented using at least one transmitter and at least one separate receiver.
  • the ED 1610 further includes one or more input/output devices 1606 or interfaces (such as a wired interface to the Internet 1550).
  • the input/output devices 1606 facilitate interaction with a user or other devices (network communications) in the network.
  • Each input/output device 1606 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.
  • the ED 1610 includes at least one memoiy 1608.
  • the memory 1608 stores instructions and data used, generated, or collected by the ED 1610.
  • the memoiy 1608 could store software or firmware instructions executed by the processing unit(s) 1600 and data used to reduce or eliminate interference in incoming signals.
  • Each memory 1608 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memoiy (RAM), read only memoiy (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memoiy stick, secure digital (SD) memoiy card, and the like.
  • RAM random access memoiy
  • ROM read only memoiy
  • SIM subscriber identity module
  • SD secure digital
  • the base station 1670 includes at least one processing unit 1650, at least one transceiver 1652, which includes functionality for a transmitter and a receiver, one or more antennas 1656, at least one memoiy 1658, and one or more input/output devices or interfaces 1666.
  • a scheduler which would be understood by one skilled in the art, is coupled to the processing unit 1650. The scheduler could be included within or operated separately from the base station 1670.
  • the processing unit 1650 implements various processing operations of the base station 1670, such as signal coding, data processing, power control, input/output processing, or any other functionality.
  • the processing unit 1650 can also support the methods and teachings described in more detail above.
  • Each processing unit 1650 includes any suitable processing or computing device configured to perform one or more operations.
  • Each processing unit 1650 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.
  • Each transceiver 1652 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1652 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 1652, a transmitter and a receiver could be separate components. Each antenna 1656 includes any suitable structure for transmitting or receiving wireless or wired signals 1690. While a common antenna 1656 is shown here as being coupled to the transceiver 1652, one or more antennas 1656 could be coupled to the transceiver(s) 1652, allowing separate antennas 1656 to be coupled to the transmitter and the receiver if equipped as separate components.
  • Each memoiy 1658 includes any suitable volatile or non-volatile storage and retrieval device(s).
  • Each input/output device 1666 facilitates interaction with a user or other devices (network communications) in the network.
  • Each input/output device 1666 includes any suitable structure for providing information to or receiving/providing information from a user, including network interface communications.
  • FIG. 17 is a block diagram of a computing system 1700 that may be used for implementing the devices and methods disclosed herein.
  • the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS).
  • Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vaiy from device to device.
  • a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc.
  • the computing system 1700 includes a processing unit 1702.
  • the processing unit includes a central processing unit (CPU) 1714, memoiy 1708, and may further include a mass storage device 1704, a video adapter 1710, and an I/O interface 1712 connected to a bus 1720.
  • CPU central processing unit
  • the bus 1720 may be one or more of any type of several bus architectures including a memoiy bus or memory controller, a peripheral bus, or a video bus.
  • the CPU 1714 may comprise any type of electronic data processor.
  • the memoiy 1708 may comprise any type of non-transitory system memory such as static random access memoiy (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memoiy (ROM), or a combination thereof.
  • the memoiy 1708 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.
  • the mass storage 1704 may comprise any type of non-transitoiy storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 1720.
  • the mass storage 1704 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.
  • the video adapter 1710 and the I/O interface 1712 provide interfaces to couple external input and output devices to the processing unit 1702.
  • input and output devices include a display 1718 coupled to the video adapter 1710 and a mouse, keyboard, or printer 1716 coupled to the I/O interface 1712.
  • Other devices may be coupled to the processing unit 1702, and additional or fewer interface cards may be utilized.
  • a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.
  • USB Universal Serial Bus
  • the processing unit 1702 also includes one or more network interfaces 1706, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks.
  • the network interfaces 1706 allow the processing unit 1702 to communicate with remote units via the networks.
  • the network interfaces 1706 may provide wireless communication via one or more transmitters/transmit antennas and one or more receivers/ receive antennas.
  • the processing unit 1702 is coupled to a local-area network 1722 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.
  • a method for mapping quality of service (QoS) flows to data radio bearers comprising: determining, by a communication device, a data volume in a queue of a first DRB; and determining, by the communication device, that the data volume in the queue of the first DRB does not reach a specified threshold, and based thereon: mapping, by the communication device, the first QoS flow to the first data radio bearer; and transmitting, by the communication device, a packet of the first QoS flow over the first data radio bearer.
  • QoS quality of service
  • the method of the first embodiment may further include receiving, by the communication device, a QoS flow to data radio bearer mapping configuration for the first data radio bearer.
  • the QoS flow to data radio bearer mapping configuration being received in a radio resource control (RRC) message.
  • RRC radio resource control
  • the method of the first embodiment may further include determining, by the communication device, a data volume in a queue of a second data radio bearer; and determining, by the communication device, that the data volume in the queue of the second data radio bearer does not exceed the specified data threshold, and based thereon: mapping, by the communication device, the QoS flow to a second data radio bearer; and transmitting, by the communication device, a packet of the QoS flow over the second data radio bearer.
  • the communication device is a user equipment (UE).
  • mapping the first QoS flow to the first data radio bearers is performed by a service data application protocol (SDAP) entity of the communication device.
  • SDAP service data application protocol
  • a method for mapping quality of service (QoS) flows to data radio bearers comprising: determining, by a communication device, a characteristic measure of a QoS flow and/or of a plurality of data radio bearers associated with the QoS flow; mapping, by the communication device, the QoS flow to one of the DRB in accordance with the characteristic measure of the QoS flow or of the DRBs; and transmitting, by the communication device, a packet of the QoS flow over the mapped data radio bearer.
  • the method of the second embodiment may further include receiving, by the communication device, a QoS flow to data radio bearer mapping configuration for the plurality of data radio bearers in a radio resource control (RRC) message.
  • RRC radio resource control
  • mapping the QoS flow to the one of the plurality of data radio bearers includes: determining, by the communication device, if the characteristic measure of the QoS flow is equal to or below a specified characteristic threshold; mapping, by the communication device, the QoS flow to a first data radio bearer in response to determining that the characteristic measure of the QoS flow is equal to or below the specified characteristic threshold; and mapping, by the communication device, the QoS flow to a second data radio bearer in response to determining that the characteristic measure of the QoS flow exceeds the specified characteristic threshold.
  • the characteristic measure comprising at least one of a maximum data burst volume, a cumulative data rate, a cumulative delay, a cumulative packet error rate, a packet size, a packet type, a number of dropped packets, a buffer size, or a QoS parameter.
  • mapping the QoS flow to the one of the plurality of data radio bearers occurs dynamically.
  • a method for generating report of connection characteristics of quality of service (QoS) flows includes: determining, by a communication device, a characteristic measure of data radio bearers (DRBs); and comparing, by the communication device, the characteristic measure of the DRBs with a specified threshold, and based thereon: generating, by the communication device, a report of connection characteristics of the QoS flows.
  • DRBs data radio bearers
  • the method of the third embodiment further includes receiving, by the communication device, a reporting configuration for the connection characteristics of the QoS flows.
  • the reporting configuration is received in a radio resource control (RRC) message.
  • the communication device includes a user equipment (UE).
  • UE user equipment
  • SDAP service data application protocol
  • the method of the third embodiment further includes determining, by the communication device, a data volume of a queue of a DRB; and determining, by the communication device, that the data volume of the queue of the DRB is meets the specified threshold, and based thereon: generating, by the communication device, a queue size report for the report of connection characteristics.
  • the method of the third embodiment further includes determining, by the communication device, a data volume transmitted in a time duration of DRBs; and determining, by the communication device, that the data volume transmitted in the time duration of the DRBs meets the specified threshold, and based thereon: generating, by the communication device, a data rate report for the report of connection characteristics.
  • a device in a fourth embodiment, includes one or more processors, and a non-transitory memoiy storage including instructions that, when executed by the one or more processors, cause the device to perform the methods of the first embodiment, the second embodiment and the third embodiment.
  • An embodiment includes mapping a QoS flow to multiple DRBs, and determining dynamically which DRB(s) packets of the QoS flow should be delivered to.
  • a maximum queue size may be configured for a DRB. Queue size is measured as the data volume in MAC/RLC/PDCP entities of a DRB, and it may be equivalent to the sum of buffer status of logical channels associated with the DRB. Packets of QoS flow are steered to DRB(s) according to their queue size, experienced data rate and reliability, etc.
  • the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution described in the present disclosure may be embodied in the form of a software product.
  • a suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitoiy computer readable medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example.
  • the software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute embodiments of the methods disclosed herein.
  • a signal may be transmitted by a transmitting unit or a transmitting module.
  • a signal may be received by a receiving unit or a receiving module.
  • a signal may be processed by a processing unit or a processing module.
  • mapping unit or module may be performed by a mapping unit or module, a reporting unit or module, a packet generating unit or module, a packet to QoS flow mapping unit or module, a QoS flow to DRB mapping unit or module, a characteristic measure unit or module, a characteristic measure comparing unit or module, a report generating unit or module, a configuring unit or module, a signaling unit or module, and/or a determining unit or module.
  • the respective units or modules may be hardware, software, or a combination thereof.
  • one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).
  • FPGAs field programmable gate arrays
  • ASICs application-specific integrated circuits

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A user equipment (UE) may map packets of a quality of service (QoS) flow to data radio bearers (DRBs) based on characteristic measures of the DRBs or characteristic measure of the packets of the QoS flow. In an embodiment, when a characteristic measure of a DRB satisfies a condition, the UE may map a data packet of the QoS flow to the DRB. In another embodiment, when a characteristic measure of one or more data packets of the QoS flow satisfies a condition, the UE may map a data packet of the QoS flow to a DRB. The UE may then transmit the data packet over the DRB. The UE may further generate a report of transmission characteristics of one or more data packets of the QoS flow when the characteristic measure satisfies a reporting condition.

Description

Methods and Apparatus for Communications Over Data Radio Bearer
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Application No.
63/ 197,165, filed on June 4, 2021 and entitled “Methods and Apparatus for Packet Flow to Data Radio Bearer Mapping,” and U.S. Provisional Application No. 63/ 197,028, filed on June 4, 2021 and entitled “Methods and Apparatus for Connection Status Exposure in Service Data Adaptation.” The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.
TECHNICAL FIELD
[0002] The present disclosure relates generally to methods and apparatus for wireless communications, and, in particular embodiments, to methods and apparatus for communications of over data radio bearer.
BACKGROUND
[0003] Current generation wireless communications systems provide high data rates for mobile communications devices to enable a rich multi-media environment for users of the mobile communications devices. The complexity of applications available to the users continues to increase, along with the need for increased throughput and lower latency.
[0004] Different packet flows from mobile applications, such as different Quality of Service (QoS) flows, have different data requirements, e.g., data rate, delay, packet error rate, etc. Data radio bearer (DRB) defines the packet treatment on the radio interface. A DRB serves packets with the same packet forwarding treatment. Hence, mapping a data flow requiring low latency to a DRB incurring large transmission delay would result in failure in delivering application satisfactorily, while mapping a data flow tolerating high packet error rate to a DRB with high reliability would result in inefficient utilization of radio resources. Therefore, it is desirable to develop techniques for packet flow transmission over DRBs with improved communication performance and efficiency.
SUMMARY
[0005] According to one aspect of the present disclosure, a method is provided that includes: determining, by a communication device, a characteristic measure of a first data radio bearer (DRB); and when the characteristic measure of the first DRB satisfies a condition, mapping, by the communication device, a first data packet of a quality of service (QoS) flow to the first DRB; and transmitting, by the communication device, the first data packet over the first DRB.
[0006] Optionally, in any of the preceding aspects, the method further includes: when the characteristic measure of the first DRB does not satisfy the condition, determining, by the communication device, whether to map the data packet of the QoS flow to a second DRB for transmission.
[0007] Optionally, in any of the preceding aspects, the method further includes: determining, by the communication device, a characteristic measure of the second DRB.
[0008] Optionally, in any of the preceding aspects, the method further includes: determining, by the communication device, that a characteristic measure of a third DRB satisfies the condition; mapping, by the communication device, a second data packet of the QoS flow to the third DRB; and transmitting, by the communication device, the second data packet over the third DRB.
[0009] Optionally, in any of the preceding aspects, the characteristic measure of the first DRB, the second DRB or the third DRB comprises one of following: a data volume in a queue of a DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or a priority of the DRB.
[0010] Optionally, in any of the preceding aspects, the method further includes: comparing, by the communication device, the characteristic measure of the first DRB with a threshold to determine whether the characteristic measure of the first DRB satisfies the condition.
[0011] Optionally, in any of the preceding aspects, the condition specifies the characteristic measure of the first DRB and the threshold.
[0012] Optionally, in any of the preceding aspects, the characteristic measure of the first DRB comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition.
[0013] Optionally, in any of the preceding aspects, the characteristic measure of the first DRB is a sum or an average of values of the characteristic measure of the first DRB for a period of time. [0014] Optionally, in any of the preceding aspects, the communication device is a user equipment (UE).
[0015] Optionally, in any of the preceding aspects, the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
[0016] According to another aspect of the present disclosure, a method is provided that includes: determining, by a communication device, a characteristic measure of data packets of a quality of service (QoS) flow; when the characteristic measure of the data packets satisfies a condition, mapping, by the communication device, a first data packet of the QoS flow to a first data radio bearer (DRB); and transmitting, by the communication device, the first data packet over the first DRB.
[0017] Optionally, in any of the preceding aspects, the method further includes: when the characteristic measure of the data packets does not satisfy the condition, mapping, by the communication device, the first data packet of the QoS flow to a second DRB; and transmitting, by the communication device, the first data packet over the second DRB.
[0018] Optionally, in any of the preceding aspects, the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
[0019] Optionally, in any of the preceding aspects, the method further includes: comparing, by the communication device, the characteristic measure of the data packets of the QoS flow with a threshold to determine whether the characteristic measure satisfies the condition.
[0020] Optionally, in any of the preceding aspects, the condition specifies the characteristic measure and the threshold.
[0021] Optionally, in any of the preceding aspects, the characteristic measure comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition. [0022] Optionally, in any of the preceding aspects, the characteristic measure is a sum or an average of values of the characteristic measure of the packets of the QoS flow for a period of time.
[0023] Optionally, in any of the preceding aspects, the communication device is a user equipment (UE).
[0024] Optionally, in any of the preceding aspects, the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
[0025] According to another aspect of the present disclosure, a method is provided that includes: determining, by a communication device, a characteristic measure of a data radio bearers (DRB) or of packets of a quality of service (QoS) flow; when the characteristic measure satisfies a condition, generating, by the communication device, a report of transmission characteristics of one or more data packets of the QoS flow.
[0026] Optionally, in any of the preceding aspects, the characteristic measure of the DRB comprises one of following: a data volume in a queue of the DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or a priority of the DRB.
[0027] Optionally, in any of the preceding aspects, the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
[0028] Optionally, in any of the preceding aspects, the method further includes: comparing, by the communication device, the characteristic measure with a threshold to determine whether the characteristic measure satisfies the condition.
[0029] Optionally, in any of the preceding aspects, the condition specifies the characteristic measure of the first DRB and the threshold.
[0030] Optionally, in any of the preceding aspects, the report comprises one or more of following: a data rate; a transmission delay; a packet waiting time; a queue size; data transmitted in a time window; number of packet errors in a time duration; time taken for successful packet transmission; or a packet dropping rate.
[0031] Optionally, in any of the preceding aspects, the communication device is a user equipment (UE).
[0032] Optionally, in any of the preceding aspects, the method further includes: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for generating the report, the configuration comprising the condition.
[0033] According to one aspect of the present disclosure, an apparatus is provided that includes a non-transitoiy memory storage comprising instructions; and one or more processors in communication with the memoiy storage, wherein the instructions, when executed by the one or more processors, cause the apparatus to perform a method in any of the preceding aspects.
[0034] According to one aspect of the present disclosure, a non-transitoiy computer-readable media is provided. The non-transitory computer-readable media stores computer instructions that when executed by one or more processors of an apparatus, cause the apparatus to perform a method in any of the preceding aspects.
[0035] An advantage of the aspects of the present disclosure is that QoS flow to DRB mapping adapts to traffic burst and fast changing radio interface conditions. This helps support low latency high throughput communication. The aspects of the present disclosure allow resources configured for a DRB to be allocated according to the instantaneous need of a QoS flow and/or DRB statuses, and enable a more efficient resource allocation in a communication system.
BRIEF DESCRIPTION OF THE DRAWINGS
[0036] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
[0037] Figure 1 is a diagram of an example communications system;
[0038] Figure 2 is a diagram of an example mapping of data packets to data radio bearers (DRBs) in a conventional manner;
[0039] Figure 3 is a flow diagram of operations occurring in a prior art technique for mapping data packets to DRBs; [0040] Figure 4 is a flow diagram of example operations occurring in matching packets of QoS flows to DRBs based on a characteristic measure according to example embodiments presented herein;
[0041] Figure 5 is a flow diagram of example operations occurring in mapping packets of a QoS flow to a DRB based on a queue size of the DRB according to example embodiments presented herein;
[0042] Figure 6 is a flow diagram of example operations occurring in mapping packets of a QoS flow to a DRB based on a cumulative characteristic measure according to example embodiments presented herein;
[0043] Figure 7 is a flow diagram of example operations occurring in configuring and mapping of QoS flows to DRBs based on a characteristic measure according to example embodiments presented herein;
[0044] Figure 8 is a flow diagram of example operations occurring in reporting connection conditions of QoS flows to applications according to example embodiments presented herein;
[0045] Figure 9 is an overview diagram of layers and sublayers involved in mapping of packets of QoS flows of applications to DRBs according to example embodiments presented herein;
[0046] Figure 10 is a flow diagram of example operations occurring in reporting connection conditions of QoS flows to applications according to example embodiments presented herein;
[0047] Figure 11 is a flow diagram of example operations occurring in configuring and reporting connection statuses of QoS flows to applications according to example embodiments presented herein;
[0048] Figure 12 is a flow diagram of example operations occurring in mapping QoS flows to DRBs based on characteristic measures of DRBs according to example embodiments presented herein;
[0049] Figure 13 is a flow diagram of example operations occurring in mapping QoS flows to DRBs based on characteristic measures of the QoS flows according to example embodiments presented herein;
[0050] Figure 14 is a flow diagram of example operations occurring in reporting connection status of a QoS flow;
[0051] Figure 15 illustrates an example communication system according to example embodiments presented herein; [0052] Figures 16A and 16B illustrate example devices that may implement the methods and teachings according to this disclosure; and
[0053] Figure 17 is a block diagram of a computing system that may be used for implementing the devices and methods disclosed herein.
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
[0054] The structure and use of disclosed embodiments are discussed in detail below. It should be appreciated, however, that the present disclosure provides many applicable concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific structure and use of embodiments, and do not limit the scope of the disclosure.
[0055] Successful transmission of a quality of service (QoS) flow depends on mapping of packets of the QoS flow to appropriate data radio bearers (DRBs) and other factors. It is desirable that QoS flows may be dynamically mapped to DRBs that meet specific requirements of different QoS flows, based on DRB statuses and QoS requirements of the QoS flows.
[0056] Embodiments of the present disclosure provide methods and apparatus for dynamic mappings of QoS flows to DRBs. A user equipment (UE) may map packets of a QoS flow to DRBs based on characteristic measures of the DRBs and/ or characteristic measure of packets of the QoS flow. In an embodiment, when a characteristic measure of a DRB satisfies a condition, the UE may map a data packet of the QoS flow to the DRB. In another embodiment, when a characteristic measure of one or more data packets of the QoS flow satisfies a condition, the UE may map a data packet of the QoS flow to a DRB. The UE may then transmit the data packet over the mapped DRB. The UE may further generate a report of transmission characteristics of one or more data packets of the QoS flow when the characteristic measure satisfies a reporting condition. The report may be used by applications of the UE in generating and processing packets to be transmitted.
[0057] Figure 1 illustrates an example communications system too.
Communications system too includes an access node 105 serving user equipments (UEs), such as UEs no, 112, 114, 116, and 118. Access node 105 is connected to a backhaul network that provides connectivity to services and the Internet. In a first operating mode, communications to and from a UE passes through access node 105. In a second operating mode, communications to and from a UE do not pass through access node 105, however, access node 105 typically allocates resources used by the UE to communicate when specific conditions are met. Communication between a UE pair in the second operating mode occurs over sidelinks, comprising uni-directional communication links. Communication between a UE and access node pair also occur over uni-directional communication links, where the communication links from the UE and to access node are referred to as uplinks, and the communication links from the access node to the UE is referred to as downlinks.
[0058] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master or primaiy eNBs (MeNBs), secondary eNBs (SeNBs), master primaiy gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on. UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE- A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na/b/g/n/ac/ad/ax/ay/be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and five UEs are illustrated in Figure 1 for simplicity.
[0059] When a communication device, e.g., a UE or an AN, has data packets to be transmitted, the data packets may be mapped into different flows (also referred to as packet flows or data flows), e.g., quality of service (QoS) flows, according to some rules. For example, packets having a common characteristics, property or QoS requirement may be mapped into one flow. In the following, QoS flows will be used as an example for illustration purpose only, and other packet flows may also be applicable. A QoS flow may include a stream of data packets that have one or more common QoS requirements. The QoS flows may then be mapped to data radio bearer (DRBs), and transmitted over the mapped DRBs. A bearer is a logical or virtual concept, and may be understood as a carrier or a link between a transmitting point and a receiving point. A bearer defines how data/signaling is treated when it travels across a network. A DRB is configured to cany user-plane traffic, e.g., user data, internet protocol packets, and so on. Some related 3GPP standards have provided specifications about mapping QoS flows to DRBs. The standards may continue to evolve. [0060] Figure 2 illustrates a diagram 200 of an example mapping of data packets to DRBs in a conventional manner. The mapping of data packets to DRBs may occur over multiple layers, including an application layer 205, a non-access stratum (NAS) layer 207, and an access stratum (AS) layer 209. In application layer 205, data packets (such as data packets 210, 211, and 212) are generated by an application. In NAS layer 207, NAS QoS rules 215 map the data packets to QoS flows, such as a QoS flow 217. In addition, QoS flow identifiers (QFIs) are applied to packets of the respective QoS flows in NAS layer 207, where packets of a single QoS flow have the same QFI. The QoS flows in this layer may be segregated into Internet Protocol (IP) flows 218 or non-IP flows 219, for example. In AS layer 209, AS rules 220 map the QoS flows to DRBs. As an example, packets with a certain QFI are mapped to a particular DRB.
[0061] Figure 3 illustrates a flow diagram of operations 300 occurring in a prior art technique for mapping data packets to DRBs. The mapping of the data packets includes mapping the data packets to QoS flows (block 305). As discussed previously, the mapping of the data packets to QoS flows occurs in the NAS layer and utilizes NAS QoS rules. Some example mappings may be found in 3GPP related standards. A QFI is also applied to the packets of each QoS flow. The packets of the QoS flows are mapped to DRBs (block 307). The mapping of packets of the QoS flows to DRBs is performed in the AS layer. As an example, packets of one QoS flow are mapped to one DRB. As another example, multiple QoS flow may be mapped to one DRB.
[0062] The mapping of the data packets to QoS flows may be based on certain QoS rules, so that packets in a QoS flow share certain common characteristics, e.g., certain requirements on data rate, delay, or reliability. In conventional 3GPP communication systems, UEs are configured with QoS flow to DRB mapping rules in a semi-static fashion. That is, mapping of QoS flows to DRBs follows the semi-statically configured mapping rules, and is not capable of dynamically adjusting mapping of QoS flows to DRBs. Thus, dynamic mapping between QoS flows and DRBs is not provided, e.g., based on characteristic of the DRBs and/or packets of the QoS flows.
[0063] Lack of dynamic mapping of QoS flows to DRBs may cause degraded transmission performance and user experience, and wasted resources. For example, the traffic burstiness of QoS flows could make a DRB heavily loaded at a time instant according to a semi-static mapping rule, while a DRB is lightly loaded when its mapped QoS flows are mostly idle.
[0064] As another example, the maximum data burst volume (MDBV) is the largest amount of data that a 5G access network (5G-AN) is required to serve within a period of a 5G-AN packet delay budget (PDB). For guaranteed bit rate (GBR) QoS flows with delay critical GBR resource type, a packet is deemed as being lost if it is delayed more than its associated PDB. The packet is also included in the packet error rate (PER) calculation unless the data burst exceeds the MDBV within the period of the PDB or the QoS flow exceeds the guaranteed flow bit rate (GFBR) . Each GBR QoS flow may be associated with an averaging window. The averaging window represents the duration over which the GFBR and the maximum flow bit rate (MFBR) are calculated (e.g., in a radio access network (RAN), AN, user plane function (UPF), UE, etc.). Table 1 below presents default priority levels, PDB, PER, averaging window size, and example services for different 5G QoS identifier (5QI) parameter values, according to 3GPP TS 23.501 "System architecture for the 5G System (5GS)," which is herein incorporated by reference.
Table 1: Example default priority levels, PDB, PER, averaging window size, and example services for different 5G QoS identifier (5QI) parameter values
Figure imgf000012_0001
[0065] Thus, in this example, successful transmission of a QoS flow depends on mapping of packets of the QoS flow to appropriate DRBs, packet delay budget, PER, and other factors. It is thus desirable to dynamically map QoS flows to DRBs that meet specific requirements of different QoS flows.
[0066] Embodiments of the present disclosure provide methods and apparatus for dynamic mappings of QoS flows to DRBs. The dynamic mappings may be based on characteristic measures of the DRBs and/or the QoS flows, such as data rate, reliability, delay, and/or any other metrics of the DRBs and/or the QoS flows. A characteristic measure may be a running sum (or summation), or average, or a result of any other applicable processing, of metrics (such as MDBV, data rate, packet error rate, delay, data volume in a queue, packet waiting time, data transmitted in a time interval, time taken for successful transmission, any other QoS metrics, etc.) over a time duration. A characteristic measure may also be a combination of multiple different characteristic metrics. In some embodiments, one or more characteristic measure of a DRB and/or a QoS flow may be assessed against one or more conditions, and when the one or more conditions are satisfied, one or more packets of the QoS flow may be mapped to the DRB and transmitted over the mapped DRB. As an example, based on a comparison of a characteristic measure of DRBs with one or more thresholds, one of a plurality of DRBs may be selected and packets of the QoS flow are mapped to the selected DRB.
[0067] Embodiments of the present disclosure have advantage of being able to dynamically map data packets of a QoS flow to DRBs. Dynamic QoS packets to DRBs can match resources configured for a DRB according to the instantaneous need of a QoS flow and DRB status, enabling a more efficient resource allocation in a communication system.
[0068] In some embodiments, a characteristic measure of a DRB may include one or more of following:
• a data volume in a queue of the DRB (also referred to as a queue size), which may be an amount of data in the queue to be transmitted over the DRB;
• a data rate of the DRB, which may be an amount of data transmitted in a unit time;
• a maximum data burst volume (MDBV) supported by the DRB;
• a packet error rate of data transmitted over the DRB;
• a transmission delay of the DRB, which may be the average time of successful transmission of packets in a DRB during a measuring period. It may include waiting time and time taken for successful transmission;
• packet waiting time of the DRB, which may be a time period that a packet waits for being transmitted; • an amount of data transmitted over the DRB in a time interval;
• time taken for successful transmission of a packet over the DRB;
• buffering time;
• a number of dropped packets during a time period;
• a number of packet errors during a time period; or
• a priority of the DRB.
[0069] In some embodiments, a characteristic measure of packets of a QoS flow may include one or more of following:
• a data rate of the QoS flow, which may be an amount of data of the QoS flow arriving for transmission in a unit time;
• a maximum data burst volume (MDBV) of the QoS flow;
• a data volume of the QoS flow, which may be an amount of data of the QoS flow in a buffer at a certain measurement time;
• a packet size of a packet of the QoS flow, which may be a size of a packet, or an average size of packets;
• a packet type of a packet of the QoS flow, e.g., IP, non-IP, video, voice, encoded, un-encoded packets, and so on, which may depend on applications;
• packet waiting time of the QoS flow, which may be a time period that a packet of the QoS flows waits for being transmitted, e.g., a time period from arrival of the packet of the QoS flow to transmission of the packet;
• a number of dropped packets of the QoS flow;
• a number of packet errors of the QoS flow;
• a priority of the QoS flow; or
• a buffer size of the QoS flow, which may be a size of a buffer buffering packets of the QoS flow.
[0070] It is noted that the “characteristic measure of packets of a QoS flow” may also be referred to as “characteristic measure of a QoS flow” in embodiments of the present. A characteristic measure of a QoS flow may be related to a packet of the QoS flow, multiple packets of the QoS flow, or the entire QoS flow. Those of ordinaiy skill in the art would recognize that the characteristic measures of DRBs and QoS flows are not limited to those listed above, and any other applicable characteristic measures of DRBs or QoS flows may also be used in embodiments of the present disclosure, without departing from the spirit and principle of the present disclosure. [0071] The dynamic QoS flows to DRBs mapping operations may be configured using signaling, such as radio resource control (RRC) signaling. However, other applicable types of signaling are possible. As an illustrative example, a UE may receive a QoS flow to DRB mapping configuration (or rule) in RRC signaling. The UE may perform QoS flow to DRB mapping according to the received configuration. The UE may be configured to switch dynamically the QoS flow to DRB mapping according to another configuration.
[0072] In some embodiments, the QoS flow to DRB mapping configuration/rule may specify one or more conditions for mapping QoS flows to DRBs. The condition may include information or criterion for determining which packet(s) of a QoS flow is to be mapped to which DRB. An example condition may include information about one or more characteristic measures to be taken (or used), and one or more thresholds of the characteristic measures to be used for determining which DRB packets of a QoS flow are to be mapped to.
[0073] As an example, a condition may specify:
• If a data rate of DRB1 > threshold, map a packet of a QoS flow to DRB1;
• If the data rate of DRB1 < = threshold, assess the next DRB.
[0074] In the above example, the next DRB will be assessed similarly to DRB1 using the same threshold or a different threshold. For example, when assessing the next DRB, e.g., DRB2, , if the data rate of DRB2 is greater than the threshold, the packet is mapped to DRB2; however, if the data rate of DRB2 is not greater than the threshold, a next DRB, e.g., DRB3, may then be assessed similarly, until a DRB satisfying the condition is found. The DRBs being assessed may be pre-determined. When no DRB is found to satisfy the condition, the packet may be mapped to a default DRB for transmission. This example maps the QoS flow to DRBs based on a characteristic measure of the DRBs, i.e., a data rate of the DRBs. Other characteristic measures of the DRBs may be used similarly. As another example, a condition may specify:
• If a data volume in a queue of DRBi < threshold, map a packet of a QoS flow to DRBi;
• If the data volume of DRBi > = threshold, assess the next DRB.
[0075] In some embodiments, a DRB may be selected from a plurality of DRBs based on whether a condition is satisfied by the DRB, and a packet of a QoS flow is mapped to the selected DRB. As an example, a condition may specify:
• Map to a DRB that has packet waiting time less than a threshold time. [0076] In this example, packet waiting time of each of a plurality of DRBs may be obtained and compared with the threshold time, and one DRB satisfying the condition may be selected for transmitting a packet of a QoS flow.
[0077] In some embodiments, different thresholds may be configured for different DRBs in a condition. For example, if a first DRB has a large buffer and a second DRB has a small buffer, a queue size threshold for the first DRB may be larger than the queue size threshold for the second DRB.
[0078] As another example, a condition may specify:
• If a packet size of a packet > threshold!, map the packet to DRBi;
• If thresholda < the packet size < = threshold!, map the packet to DRB2;
• If the packet size < = threshold2, map the packet to DRB3.
[0079] The above example maps packets of a QoS flow to DRBs based on a characteristic measure of a QoS flow, i.e., a packet size of a packet of the QoS flow. Other characteristic measures of the packets of the QoS flow may be used similarly. As another example, a condition may specify:
• If a data volume of the QoS flow > threshold, map a packet of the QoS flow to DRBi or DRB2; else, map the packet to DRB3.
[0080] In some embodiments, packets of a QoS flow may be mapped to DRBs based on a characteristic measure of the DRBs and a characteristic measure of packets of the QoS flow. As an example, a condition may specify:
• If a data volume of the QoS flow > threshold!, assess DRBi, DRB2, DRB3 o If priority of DRBi > threshold2, map a packet to DRBi; o Else, if priority of DRB2 > threshold2, map the packet to DRB2. o Else, if priority of DRB3 > threshold2, map the packet to DRB3.
• If the data volume of the QoS flow< = threshold!, assess DRB4, DRB5 o If priority of DRB4 > threshold2, map the packet to DRB4; o Else, if priority of DRB5 > threshold2, map the packet to DRB5.
[0081] The above example conditions are merely provided for illustration purposes. Those of ordinary skill in the art would recognize that many variations, alternatives and embodiments may be applicable for configuring the conditions by use of characteristic measures of DRBs and/ or QoS flows. [0082] In some embodiments, a service data application protocol (SDAP) entity may perform dynamic mapping of QoS flows to multiple DRBs for packets of a QoS flow, based on one or more configured mapping conditions. As an example, when a DRB queue size is used as a characteristic measure, , the SDAP entity may operate as follows:
An SDAP protocol data unit (PDU) is generated for an SDAP service data unit (SDU) from an upper layer for a QoS flow;
If the queue size of a DRB in the configured mapping rule is smaller than a configured threshold, the SDAP entity will map the SDAP PDU to the DRB.
[0083] Figure 4 illustrates a flow diagram of example operations 400 occurring in dynamic mapping of packets of QoS flows to DRBs based on a characteristic measure of DRBs and/or the QoS flow. Operations 400 may be indicative of operations occurring in a device, such as a UE, as the device dynamically maps packets of a QoS flow to DRBs based on a characteristic measure.
[0084] Operations 400 begin with the UE receiving configuration of QoS flow to DRB mappings (block 405). The configuration of QoS flow to DRB mappings may be received in RRC signaling from an access node serving the UE, for example. As an example, a QoS flow (packets of the QoS flow) may be mapped to two or more DRBs, where a particular packet of the QoS flow to DRB mapping is based on a characteristic measure of the QoS flow or the DRBs. Examples of characteristic measures include data rate, priority, reliability, queue size, delay, data transmitted in a time interval, packet waiting time, time taken for successful transmission, or any other QoS metrics as described above.
[0085] The UE maps data packets to QoS flows (block 407). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow. The UE maps the QoS flows to DRBs (block 409). The mapping of the QoS flows to DRBs may include the UE comparing a characteristic measure of a DRB or a QoS flow to a threshold, where the threshold may differ among different DRBs. As an example, if a first DRB has a large buffer and a second DRB has a small buffer, the queue size threshold for first DRB may be larger than the queue size threshold for the second DRB.
[0086] Figure 5 illustrates a flow diagram of example operations 500 occurring in dynamic mapping of packets of a QoS flow to a DRB based on a DRB queue size. Operations 500 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of a QoS flow to a DRB with dynamic switching based on DRB queue size.
[0087] Operations 500 begin with the device mapping data packets to QoS flows (block 505). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow. The device determines the current queue size of a DRB (block 507). The device may determine the queue status of the DRB based on the buffered data at medium access control/radio link control/packet data convergence protocol (MAC/RLC/PDCP) entities associated with the DRB. Alternatively, the device may sum the buffer status of logic channels associated with the DRB.
[0088] The device performs a check to determine if the queue size of the DRB meets a specified threshold (block 509). The specified threshold may be specified in the configuration of QoS flow to DRB mappings, for example. In an embodiment, the specified threshold may be based on the maximum queue size allowed for the DRB. In an embodiment, the specified threshold may be based on the maximum delay that a packet of a QoS flow can tolerate. The specified threshold may specify a cumulative data volume or time spent within data buffers of the MAC/RLC/PDCP entities of the DRB.
[0089] If the data volume in the queue of the DRB does not exceed the specified threshold, the device maps one or more packets of a QoS flow to the DRB (block 511). In other words, if the data stored in the queue of the DRB is less than the specified threshold, the device may deliver more data to the DRB. The device transmits packets of the QoS flow over the mapped DRB (e.g., a first DRB) (block 513).
[0090] If the queue size of the DRB meets or exceeds the specified threshold, the device does not map the packets of the QoS flow to the DRB. Instead, the packets of the QoS flow may either be buffered at the SDAP entity or mapped to another DRB (e.g., a second DRB) (block 515). In other words, if the data volume stored in the queue of the first DRB meets (e.g., is equal to or higher than) the specified threshold, mapping the packets of the QoS flow to the first DRB would increase the buffering in the first DRB to an undesirable level, and data mapped to the DRB in the future would thus experience longer transmission delay. Hence, the packets of the QoS flow may be mapped to another DRB (e.g., the second DRB), if the second DRB does not have a configured queue size threshold, or the threshold is met by the second DRB. In another example, the packets of the QoS flow may be stored in the SDAP entity temporarily and wait to be transmitted over the first DRB. [0091] Although the discussion above focuses on situations where a QoS flow is mapped to one of two DRBs, the example embodiments presented herein are operable with situations where one of more QoS flows is mapped to one of three or more DRBs. Therefore, the focus on a QoS flow being mapped to one of two DRBs should not be construed as being limiting to the scope of the example embodiments.
[0092] As discussed previously, the queue size is merely a single example of a characteristic measure of the DRB. The example embodiments are operable with other characteristic measures, which may include data rate, latency, reliability, data transmitted in a time interval, number of dropped packet in a time duration, buffering time, or any other QoS metrics as described previously.
[0093] Figure 6 illustrates a flow diagram of example operations 600 occurring in mapping packets of a QoS flow to a DRB based on a cumulative characteristic measure of the QoS flow. Operations 600 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of the QoS flow to one or more DRBs based on the cumulative characteristic measure.
[0094] Operations 600 begin with the device mapping data packets to QoS flows (block 605). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow. The device determines the cumulative characteristic measure of the QoS flow (block 607). The characteristic measure may be one or more of MDBV, data rate, latency, delay, packet error, dropped packet, any other QoS metrics, etc., as described above. In an embodiment, the cumulative characteristic measure may be a combination of multiple metrics of the QoS flow. As an example, the cumulative characteristic measure may include a data rate of the QoS flow and a packet size of the QoS flow. In another embodiment, the cumulative characteristic measure may be a cumulative measure of a characteristic of the QoS flow during a period of time or for a number of packets of the QoS flow. As an example, if the characteristic measure is a data rate, the cumulative characteristic measure may be a cumulative data rate, which may be defined as a sum of data rates of the QoS flow during a period of time. As another example, if the characteristic measure is an amount of data transmitted in a time duration, the cumulative characteristic measure may be cumulative data transmitted during a period of time, which may be defined as a sum of transmitted data during the period of time. As another example, if the characteristic measure is a packet size, the cumulative characteristic measure may be a cumulative packet size, which may be defined as an average packet size of some or all packets of the QoS flow. Other cumulative characteristic measures may be similarly defined.
[0095] The device performs a check to determine if the cumulative characteristic measure of the QoS flow meets a specified threshold (block 609). The specified threshold may be specified in the configuration of QoS flow to DRB mappings, for example. In an embodiment, the specified threshold may be based on the characteristic measure to be used, e.g., the maximum sum of data rates of the QoS flow, or the maximum sum of transmitted data of the QoS flow in a time duration.
[0096] If the cumulative characteristic measure of the QoS flow meets the specified threshold, e.g., below the specified threshold in this example, the device maps a packet of the QoS flow to a first DRB (block 611). The device transmits the packet of the QoS flow over the mapped DRB (e.g., the first DRB) (block 617).
[0097] If the cumulative characteristic measure of the DRBs does not meet the specified threshold, e.g., is equal to or exceeds the specified threshold in this example, the device may either buffer one or more packets of the QoS flow at an SDAP entity of the first DRB, or map one or more packets of the QoS flow to a second DRB, e.g., a DRB configured with default or backup characteristic parameters (block 615). The device transmits a packet of the QoS flow over the mapped DRB (e.g., the second DRB) (block 617). As an example, packets of the QoS flow may be temporarily buffered in the SDAP entity, i.e., not delivered to DRBs immediately, if the cumulative characteristic measure of the QoS flow does not meet or exceeds the specified threshold indicative of what is required by the QoS flow.
[0098] The threshold, the first DRB and the second DRB may be specified as a condition in a configuration of QoS flow to DRB mappings. As an example, a condition may specify:
• If an average data volume of the QoS flow during a period of time < threshold, map a packet of the QoS flow to DRBi; else, buffer the packet (or map the packet to DRB2).
[0099] As another example, a condition may specify:
• If a data volume of the QoS flow < threshold and a packet type is type 1, map a packet of the QoS flow to DRBi;
• If the data volume of the QoS flow < threshold and a packet type is type 2, map a packet of the QoS flow to DRB2; • Else, buffer the packet (or map the packet to DRB3) .
[0100] The above example conditions are merely provided for illustration purposes. Those of ordinaiy skill in the art would recognize that many variations, alternatives and embodiments for the conditions may be applicable without departing the spirit and principle of the present disclosure. Further, although Figure 6 illustrates a method for mapping packets of a QoS flow to DRBs based on a cumulative characteristic measure of the QoS flow, those of ordinary skill in the art would recognize that similar methods may be provided for mapping packets of a QoS flow to DRBs based on a cumulative characteristic measure of DRBs, or based on cumulative characteristic measures of the QoS flow and DRBs.
[0101] Figure 7 illustrates a flow diagram of example operations 700 occurring in configuring and dynamic mapping of QoS flows to DRBs based on a characteristic measure of QoS flows. Operations 700 may be indicative of operations occurring in a device, such as a UE, as the device configures and maps the QoS flow to DRBs based on a characteristic measure of the QoS flow.
[0102] Operations 700 begin with the device receiving a configuration of QoS flow to DRB mappings (block 705). The configuration of QoS flow to DRB mappings may be received in RRC signaling. The RRC signaling may be received from an access node serving the UE. The QoS flow may be mapped to two or more DRBs based on characteristic measures of packets of the QoS flow. Examples of characteristic measures include MDBV, a data rate, a data volume, a packet size, a packet type, packet waiting time, a data buffer size (for a QoS flow), priority of a QoS flow, or any other QoS metrics, etc. as described above.
[0103] The UE maps data packets to QoS flows (block 707). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow. The UE determines the characteristic measure of packets of the QoS flow (block 709). The characteristic measure may be determined by measuring the QoS flow (or packets of the QoS flow) over an averaging window, or checking the size or type of packets of the QoS flow, for example.
[0104] The UE maps the QoS flow to a DRB in accordance with the characteristic measure of the QoS flow (block 711). As an example, the UE compares the characteristic measure of the QoS flow with a threshold and maps the QoS flow to one of the DRBs in accordance with the result of the comparison. The UE transmits a packet of the QoS flow over the mapped DRB (block 713). As an example, the characteristic measure of the QoS flow may be a packet size. A packet may be mapped to one DRB, if its size is below the threshold, and the packet may be mapped to another DRB, if its size is equal to or larger than the threshold. As another example, the characteristic measure of the QoS flow may be packet waiting time. A packet may be mapped to one DRB, if its waiting time is below the threshold, and the packet may be mapped to another DRB, if its waiting time is equal to or larger than the threshold. The threshold may be pre-defined per DRB, or generally for multiple DRBs to which the QoS flow is to be mapped.
[0105] Alternative comparisons may be possible. As an example, rather than determining if a characteristic measure is equal to or exceeds a specified threshold, the comparison may determine whether the characteristic measure is below the specified threshold. The comparison may also be reversed, such as the comparison determines whether the characteristic is larger than the specified threshold, etc.
[0106] One or more QoS flows may be mapped to a same DRB. Separate priorities may be configured to QoS flows for their mapping to the DRB. When packets of the QoS flows are mapped to a DRB, packets of the QoS flow with higher priority may be mapped to the DRB first, and packets of the QoS flow with lower priority may be mapped to the DRB afterwards. A volume threshold may be configured for a QoS flow together with the priority for mapping. The volume threshold may be the maximum amount of data, e.g., the number of bytes of the data or the number of packets of the QoS flow, that can be mapped to a DRB when it is the turn of the QoS flow to perform mapping according to the priority. The volume threshold may be subject to the restriction of maximum queue size of the DRB. That is, the maximum amount of data of a QoS flow mapped to a DRB should make the queue of the DRB exceed the maximum queue size of the DRB for the QoS flow.
[0107] Many applications support adaptive encoders, which may generate coded data traffic at different data rates. Adaptive streaming applications adjust the speed needed to stream media content, such as audio and video, according to different connection conditions. For example, streaming may be done at a higher data rate with better resolution when connection is good. On the other hand, streaming speed may be reduced when connection deteriorates with more congestion and longer delay. Packets from applications are served as Quality of Service (QoS) flows in a 5G system. As described above, packets generated by application(s) are mapped to QoS flows, and the QoS flows are mapped to DRBs. A DRB defines the packet treatment (i.e., how a packet is transmitted, e.g., how fast, or how reliable the packet is to be transmitted) on a radio interface (e.g., between a transmitting device and a receiving device/ network). A DRB serves packets with the same packet forwarding treatment. QoS flows are transmitted using DRBs over the radio interface. In order to support adaptive streaming, connection conditions/ statuses of the radio interface, such as data rate, delay, packet error rate, etc., need to be exposed to the applications. An application may adjust its packet generation, e.g., a packet generation rate, based on the connection conditions/statuses of the radio interface, in order to adaptively streaming data packets. Therefore, there is a need for methods and apparatus for transmission capability exposure in service data adaptation, i.e., to indicate a connection condition of a QoS flow to applications in use of the QoS flow, so that those applications may adjust their output data, or shape their service traffic accordingly.
[0108] In the following, the terms “connection condition”, “connection status”, “transmission condition”, and “transmission status” may be used interchangeably. The connection (or transmission) conditions/statuses of the radio interface may be represented or indicated by characteristic measures of DRBs over which QoS flows are transmitted, or by characteristic measures of packets of QoS flows. A connection condition/status may be determined and reported specifically for packets, for one or more QoS flows, or for one or more DRBs, based on characteristic measures of DRBs or QoS flows. The characteristic measures of the DRBs or the QoS flows may include one or more characteristic measures of DRBs or QoS flows as described above, and/or any other measures related to packet transmissions. These characteristic measures are also referred to as transmission characteristics, connection characteristics, or transmission statistics, in the following description, as they reflect the connection statuses of the air interface. The transmission characteristics may be measured and reported to one or more applications, and used by the one or more applications in generating or outputting data packets.
[0109] According to an example embodiment, methods and apparatus are provided for updating transmission characteristics to applications. The updating of the transmission characteristics may be performed dynamically, and performed by reporting the transmission characteristics to the applications. The dynamic updates may be based on one or more characteristic measures of DRBs and/or QoS flows, such as data rate, reliability, delay, queue size, time taken to successfully transmit packets, data transmitted in a time interval, number of dropped packets, number of packet errors, any QoS metrics, etc. As described above, a characteristic measure may be a running sum (or summation), or average, or a result of any processing, of a characteristic metric (such as data rate, packet error rate, delay, queue size, data transmitted in a time interval, number of dropped packets, number of packet errors, any other QoS metrics, etc.) over a time duration, and/or a combination of multiple different characteristic metrics.
[ono] In some embodiments, one or more transmission characteristics of DRBs or QoS flows may be measured, and one or more reports may be generated and reported to one or more applications, when a reporting condition or criterion (reporting trigger condition/criterion) is satisfied. In an embodiment, based on a comparison of one or more characteristic measures of QoS flows or DRBs with one or more thresholds, one or a plurality of reports may be made to selected applications. In another embodiment, one or a plurality of reports may be made periodically to applications according to configured time intervals. A report may include one or more characteristic measures of one or more QoS flows or one or more DRBs. The reported characteristic measures reflect a connection or transmission status of a QoS flow. The report enables an application to update the connection or transmission status of the QoS flow, i.e., transmission characteristics/ statistics of data packets, based on which the application may adjust its packet generation.
[out] The reporting of transmission characteristics for QoS flows and/or DRBs to applications may be configured using signaling, such as radio resource control (RRC) signaling. However, other types of signaling are possible. As an illustrative example, reporting of transmission status of QoS flows to applications is configured using RRC signaling. The configuration also specifies a reporting trigger condition, such as characteristic measures, as well as thresholds corresponding to one or more characteristic measures used in the comparison of the characteristic measures. As an illustrative example, a service data application protocol (SDAP) entity may perform status update of QoS flows to applications, based on a queue size of a DRB. The SDAP entity may operate as follows:
If the queue size of a DRB in reporting configuration is equal to or larger than a configured threshold, the SDAP entity reports transmission characteristics of QoS flows transmitted over the DRB to applications.
[0112] An embodiment method may include collecting transmission characteristics of DRBs carrying packets of QoS flows, and determining a connection condition for a QoS flow. As an example, transmission characteristics may be measured on data volume in a queue of a DRB. A queue size may be measured as the data volume in MAC/RLC/PDCP entities of a DRB, and it may be equivalent to the sum of buffer status of logical channels associated with the DRB. Transmission characteristics may also be measured on a data volume transmitted in a time duration, a packet error rate of the transmission, the time taken for packets to be successfully transmitted, the number of dropped packets, the time for packets to be mapped from a QoS flow to one or more DRBs, etc. Connection condition of a QoS flow may be determined based on transmission characteristics of data radio bearers. Connection condition of a QoS flow may be measures of data rate, transmission delay, packet error rate, data volume in a time window, average queue size, etc. This helps support low latency high throughput communication.
[0113] Figure 8 illustrates a flow diagram of example operations 800 occurring in dynamic update of transmission status of QoS flows to applications based on a characteristic measure. Operations 800 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of QoS flows to DRBs.
[0114] Operations 800 begin with the UE receiving a configuration of QoS flow to DRB mappings (block 805). The configuration of QoS flow to DRB mappings maybe received in RRC signaling from an access node serving the UE, for example. As an example, a QoS flow may be mapped to two or more DRBs, where a particular QoS flow to DRB mapping is based on a characteristic measure of the DRBs as described above. Examples of characteristic measures include data rate, priority, reliability, queue size, delay, data transmitted in a time interval, number of dropped packets, number of packet errors, any other QoS metrics, etc.
[0115] The UE maps data packets to QoS flows (block 807). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow. The UE maps the QoS flows to DRBs (block 909). The mapping of the QoS flows to DRBs, as described above, may include the UE comparing a characteristic measure of a DRB or a QoS flow to a threshold, where the threshold may differ among different DRBs, for example.
[0116] The UE generates reports of connection status of QoS flows (block 811). The report of connection status of QoS flows may include one or more characteristic measures of QoS flows or DRBs, such as data rate, reliability, delay, data volume in a time interval, number of packet errors in a time interval, queue size, number of dropped packets, any other QoS metrics, etc. Ttrigger events of generating reports of transmission statistics may include the UE comparing characteristic measures of DRBs or QoS flows to a threshold, where the threshold may differ between different QoS flows or DRBs. The updates of transmission statistics of QoS flows may also be done periodically at specified time intervals. Event triggering and periodic reporting can be configured together for update of connection status reporting to applications. [0117] Conditions (or events) for triggering reporting of connection statuses of QoS flows (also referred to as reporting trigger conditions or events, or trigger conditions/events) may be configured based on characteristic measures of QoS flows and/or DRBs. Example trigger conditions/events may include:
• If a characteristic measure of packets of a QoS flow satisfies a criterion, report a connection status of the QoS flow.
• If a characteristic measure of a DRB satisfies a criterion, report a connection status of a QoS flow with packet transmitted over the DRB.
• If a characteristic measure of packets of a QoS flow satisfies a first criterion, and a characteristic measure of a DRB (over which packet of the QoS flow are transmitted) satisfies a second criterion, report a connection status of the QoS flow.
[0118] The above example trigger conditions are merely provided for illustration purposes. Those of ordinaiy skill in the art would recognize that many variations, alternatives and embodiments may be applicable for configuring the reporting trigger conditions by use of characteristic measures of DRBs and/ or QoS flows. A criterion may be satisfied when a characteristic measure is greater than a threshold, less than a threshold, equal to a threshold, within a threshold range, or an applicable combination thereof. As described above, the characteristic measure may be a cumulative characteristic measure.
[0119] Figure 9 is a diagram 900 of overview of sublayers involved in mapping of packets of QoS flows of applications to DRBs. As shown in Figure 9, application data/packets of different data rates (e.g., high data rate, median data rate, and low data rate) may be generated according to connection statuses of QoS flows in the application layer. The application data/packets are mapped to different QoS flows in the SDAP sublayer. The QoS flows are mapped to DRBs in the PDCP/RLC/MAC sublayers for transmission according to uplink (UL) grant and logical channel prioritization (LCP), for example. The UL grant, for example, indicates scheduled time and radio resources for uplink transmissions. The LCP, for example, indicates how transmission resources are allocated among different DRBs. Feedback data (i.e., transmission characteristic measures) may be provided across the layers and sublayers to update the transmission characteristics of the application data. As an example, data rate and queue size information may be measured and fed back from the PDCP/RLC/MAC sublayers to the SDAP sublayer. Data rate and latency (e.g., packet transmission delay) information may be generated by the SDAP sublayer based on the data rate and queue size information, and fed back from the SDAP sublayer to the application layer. The information about the data rate and latency information may be specifically for one or more QoS flows related to the applications. The data rate and queue size information may be measured based on characteristic measures of one or more DRBs and/ or one or more QoS flows.
[0120] Figure 10 illustrates example operations 1000 occurring in exposing QoS flows’ connection status information of data rate and latency to an application based on measures of DRB queue sizes and data rates. Other characteristic measure may also be used. Operations 1000 may be indicative of operations occurring in a device, such as a UE, as the device maps packets of QoS flows (serving application data) to DRBs. Operations 900 may occur in the layers and sublayers as shown in Figure 9.
[0121] Operations 1000 begin with the SDAP entity of the device receiving feedback measures of characteristics of DRBs, i.e., data rates and queue sizes of the DRBs, e.g., from the MAC (or RLC, or PDCP) entity of the device, and generating connection status information (block 1005). The MAC (or RLC, or PDCP) entity feeds back characteristic measures of the DRBs, i.e., measures of the data rates and queue sizes, to the SDAP entity, and the SDAP entity generates connection status information of data rate and latency for QoS flows based on the characteristic measures of the DRBs, for example. The connection status information of data rate and latency for QoS flows is fed back to the application layer of the device. The application may generate data packets of one or more of the QoS flows based on the connection status. The mapping of data packets of the application to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow.
[0122] The device may map the QoS flow to DRBs using the embodiments described above, e.g., in Figures 5-7. As an example, the device determines the current queue size of a DRB (block 1007). The device may determine the queue size of the DRB based on the buffered data at MAC/RLC/PDCP entities associated with the DRB, for example. Alternatively, the device may sum the buffer status of logic channels associated with the DRB. The device performs a check to determine if the queue size of the DRB exceeds a specified threshold (block 1009). The specified threshold may be specified in the configuration of the QoS flows to DRBs mappings, for example. In an embodiment, the specified threshold may be based on the maximum queue size allowed for a QoS flow on the DRB. In an embodiment, the specified threshold may be based on the maximum delay a packet of a QoS flow can tolerate. The specified threshold may specify a cumulative data volume within data buffers of MAC/RLC/PDCP entities of the DRB. Alternative comparisons may be possible. As an example, rather than determining if the queue size simply exceeds the specified threshold, the comparison may determine if the queue size is greater than or equal to the specified threshold. The comparison may also be reversed, such as the comparison determines if the queue volume is less than the specified threshold, etc.
[0123] If the data volume in the queue of the DRB satisfies, e.g., does not exceed, the specified threshold, the device maps the packets of the QoS flow to the DRB (block ton). In other words, if the data stored in the queue of the DRB is less than the specified threshold, the device may deliver more data of the QoS flow to the DRB. And the device transmits packets of the QoS flow over the mapped DRB (e.g., the first DRB) (block 1013).
[0124] If the queue size of the DRB meets or exceeds the specified threshold, the device generates transmission reports of the QoS flow being mapped to the DRB (block 1015). In other words, if the data volume stored in the queue of the first DRB meets (e.g., is equal to or higher than) the specified threshold, mapping packets of the QoS flow over the first DRB may increase the buffering in the first DRB to an undesirable level, so data mapped to the DRB in future may experience longer transmission delay. Hence, connection status information is updated about the data rate and latency in the transmission of packets of the QoS flow. The packets of the QoS flow may be mapped to another DRB, if this DRB does not have a configured queue size threshold, or the threshold has not been met (block 1017). Or alternatively, the packets of the QoS flow may be stored in the SDAP entity temporarily (block 1017).
[0125] As discussed previously, the queue size is a single example of a characteristic measure of the DRB. The example embodiments are operable with other characteristic measures, which may include data rate, latency, packet buffering time, number of packet errors, data transmitted in a time window, time taken for successful transmission, number of dropped packets, any other QoS metrics, etc.
[0126] Figure 11 illustrates a flow diagram of example operations 1100 occurring in configuring and dynamic reporting of QoS flows’ transmission status on a characteristic measure. Operations 1100 maybe indicative of operations occurring in a device, such as a UE, as the device configures and maps QoS flows to DRBs based on a characteristic measure of the QoS flows or the DRBs.
[0127] Operations 1100 begin with the device receiving a configuration of QoS flow connection status reporting (block 1105). The configuration of QoS flow connection status reporting may be received in RRC signaling. The RRC signaling may be received from an access node serving the UE. The QoS flow connection status reporting may be triggered based on one or more characteristic measures of packets of QoS flows or packets in DRBs. Examples of characteristic measures include data rate, packet size, packet type, packet waiting time, queue size, data transmitted in a time window, number of packet errors in a time duration, time taken for successful packet transmission, number of dropped packets, any other QoS metrics, etc.
[0128] The UE maps data packets to QoS flows (block 1107). The mapping of data packets to QoS flows may be in accordance with NAS QoS rules. The packets of a single QoS flow are applied with a QFI associated with the QoS flow.
[0129] The SDAP entity in the UE determines one or more characteristic measures for a QoS flow connection status report (block 1109). The SDAP entity in the UE generates a status report of QoS flows in accordance with the characteristic measures of packets of the QoS flows (block 1111). As an example, the UE compares a characteristic measure with a threshold and updates (i.e., generates and reports) connection status information of a QoS flow if the characteristic measure is equal to or exceeds the threshold. The characteristic measure may be related to the QoS flow, or to one or more DRBs over which packets of the QoS flow are transmitted. The connection status reporting may include information of the QoS flow, such as data rate, transmission delay, packet waiting time, queue size, data transmitted in a time window, number of packet errors in a time duration, time taken for successful packet transmission, packet dropping, etc. In an embodiment, one connection status report may be generated and reported for one QoS flow, and the reporting trigger condition may be based on one or more characteristic measures related to the QoS or related to one or more DRBs over which packets of the QoS flow are transmitted.
[0130] Figure 12 is a flow diagram of example operations 1200 occurring in mapping QoS flows to DRBs based on characteristic measures of DRBs according to example embodiments presented herein. Operations 1200 maybe indicative of operations occurring in a device, such as a UE, as the device maps QoS flows to DRBs based on a characteristic measure of the DRBs. The UE determines a characteristic measure of a first data radio bearer (DRB) (block 1202). When the characteristic measure of the first DRB satisfies a condition, the UE maps a first data packet of a quality of service (QoS) flow to the first DRB, and transmits the first data packet over the first DRB (block 1204).
[0131] Figure 13 is a flow diagram of example operations 1300 occurring in mapping QoS flows to DRBs based on characteristic measures of the QoS flows according to example embodiments presented herein. Operations 1300 may be indicative of operations occurring in a device, such as a UE, as the device maps QoS flows to DRBs based on a characteristic measure of the QoS flows. The UE determines a characteristic measure of data packets of a quality of service (QoS) flow (block 1302). When the characteristic measure of the data packets satisfies a condition, the UE maps a first data packet of the QoS flow to a first data radio bearer (DRB), and transmits the first data packet over the first DRB (block 1304).
[0132] Figure 14 is a flow diagram of example operations 1400 occurring in reporting connection status of a QoS flow. Operations 1400 may be indicative of operations occurring in a device, such as a UE, as the device reports connection status of a QoS flow. The UE may determine a characteristic measure of a data radio bearers (DRB) or of packets of a quality of service (QoS) flow (block 1402). When the characteristic measure satisfies a condition, the UE generates a report of transmission characteristics of one or more data packets of the QoS flow (block 1404).
[0133] Figure 15 illustrates an example communication system 1500. In general, the system 1500 enables multiple wireless or wired users to transmit and receive data and other content. The system 1500 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).
[0134] In this example, the communication system 1500 includes electronic devices (ED) 15103-15100, radio access networks (RANs) I52oa-i52ob, a core network 1530, a public switched telephone network (PSTN) 1540, the Internet 1550, and other networks 1560. While certain numbers of these components or elements are shown in Figure 15, any number of these components or elements may be included in the system 1500.
[0135] The EDs 15103-15100 are configured to operate or communicate in the system 1500. For example, the EDs 15103-15100 are configured to transmit or receive via wireless or wired communication channels. Each ED 15103-15100 represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, or consumer electronics device.
[0136] The RANs I52oa-i52ob here include base stations 1570a- 1570b, respectively. Each base station 1570a- 1570b is configured to wirelessly interface with one or more of the EDs 15103-15100 to enable access to the core network 1530, the PSTN 1540, the Internet 1550, or the other networks 1560. For example, the base stations i570a-i570b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNodeB), a Next Generation (NG) NodeB (gNB), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs 15103-15100 are configured to interface and communicate with the Internet 1550 and may access the core network 1530, the PSTN 1540, or the other networks 1560.
[0137] In the embodiment shown in Figure 15, the base station 1570a forms part of the RAN 1520a, which may include other base stations, elements, or devices. Also, the base station 1570b forms part of the RAN 1520b, which may include other base stations, elements, or devices. Each base station I57oa-i57ob operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MIMO) technology may be employed having multiple transceivers for each cell.
[0138] The base stations 1570a- 1570b communicate with one or more of the EDs 15103-15100 over one or more air interfaces 1590 using wireless communication links. The air interfaces 1590 may utilize any suitable radio access technology.
[0139] It is contemplated that the system 1500 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.
[0140] The RANs I52oa-i52ob are in communication with the core network 1530 to provide the EDs 15103-15100 with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs I52oa-i52ob or the core network 1530 may be in direct or indirect communication with one or more other RANs (not shown). The core network 1530 may also serve as a gateway access for other networks (such as the PSTN 1540, the Internet 1550, and the other networks 1560). In addition, some or all of the EDs 15103-15100 may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 1550. [0141] Although Figure 15 illustrates one example of a communication system, various changes may be made to Figure 15. For example, the communication system 1500 could include any number of EDs, base stations, networks, or other components in any suitable configuration.
[0142] Figures 16A and 16B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, Figure 16A illustrates an example ED 1610, and Figure 16B illustrates an example base station 1670. These components could be used in the system 1500 or in any other suitable system.
[0143] As shown in Figure 16A, the ED 1610 includes at least one processing unit 1600. The processing unit 1600 implements various processing operations of the ED 1610. For example, the processing unit 1600 could perform signal coding, data processing, power control, input/output processing, or any other functionality enabling the ED 1610 to operate in the system 1500. The processing unit 1600 also supports the methods and teachings described in more detail above. Each processing unit 1600 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1600 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.
[0144] The ED 1610 also includes at least one transceiver 1602. The transceiver 1602 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 1604. The transceiver 1602 is also configured to demodulate data or other content received by the at least one antenna 1604. Each transceiver 1602 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 1604 includes any suitable structure for transmitting or receiving wireless or wired signals 1690. One or multiple transceivers 1602 could be used in the ED 1610, and one or multiple antennas 1604 could be used in the ED 1610. Although shown as a single functional unit, a transceiver 1602 could also be implemented using at least one transmitter and at least one separate receiver.
[0145] The ED 1610 further includes one or more input/output devices 1606 or interfaces (such as a wired interface to the Internet 1550). The input/output devices 1606 facilitate interaction with a user or other devices (network communications) in the network. Each input/output device 1606 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications. [0146] In addition, the ED 1610 includes at least one memoiy 1608. The memory 1608 stores instructions and data used, generated, or collected by the ED 1610. For example, the memoiy 1608 could store software or firmware instructions executed by the processing unit(s) 1600 and data used to reduce or eliminate interference in incoming signals. Each memory 1608 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memoiy (RAM), read only memoiy (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memoiy stick, secure digital (SD) memoiy card, and the like.
[0147] As shown in Figure 16B, the base station 1670 includes at least one processing unit 1650, at least one transceiver 1652, which includes functionality for a transmitter and a receiver, one or more antennas 1656, at least one memoiy 1658, and one or more input/output devices or interfaces 1666. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 1650. The scheduler could be included within or operated separately from the base station 1670. The processing unit 1650 implements various processing operations of the base station 1670, such as signal coding, data processing, power control, input/output processing, or any other functionality. The processing unit 1650 can also support the methods and teachings described in more detail above. Each processing unit 1650 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1650 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.
[0148] Each transceiver 1652 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1652 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 1652, a transmitter and a receiver could be separate components. Each antenna 1656 includes any suitable structure for transmitting or receiving wireless or wired signals 1690. While a common antenna 1656 is shown here as being coupled to the transceiver 1652, one or more antennas 1656 could be coupled to the transceiver(s) 1652, allowing separate antennas 1656 to be coupled to the transmitter and the receiver if equipped as separate components. Each memoiy 1658 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input/output device 1666 facilitates interaction with a user or other devices (network communications) in the network. Each input/output device 1666 includes any suitable structure for providing information to or receiving/providing information from a user, including network interface communications.
[0149] Figure 17 is a block diagram of a computing system 1700 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vaiy from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1700 includes a processing unit 1702. The processing unit includes a central processing unit (CPU) 1714, memoiy 1708, and may further include a mass storage device 1704, a video adapter 1710, and an I/O interface 1712 connected to a bus 1720.
[0150] The bus 1720 may be one or more of any type of several bus architectures including a memoiy bus or memory controller, a peripheral bus, or a video bus. The CPU 1714 may comprise any type of electronic data processor. The memoiy 1708 may comprise any type of non-transitory system memory such as static random access memoiy (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memoiy (ROM), or a combination thereof. In an embodiment, the memoiy 1708 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.
[0151] The mass storage 1704 may comprise any type of non-transitoiy storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 1720. The mass storage 1704 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.
[0152] The video adapter 1710 and the I/O interface 1712 provide interfaces to couple external input and output devices to the processing unit 1702. As illustrated, examples of input and output devices include a display 1718 coupled to the video adapter 1710 and a mouse, keyboard, or printer 1716 coupled to the I/O interface 1712. Other devices may be coupled to the processing unit 1702, and additional or fewer interface cards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device. [0153] The processing unit 1702 also includes one or more network interfaces 1706, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 1706 allow the processing unit 1702 to communicate with remote units via the networks. For example, the network interfaces 1706 may provide wireless communication via one or more transmitters/transmit antennas and one or more receivers/ receive antennas. In an embodiment, the processing unit 1702 is coupled to a local-area network 1722 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.
[0154] The following are some more embodiments.
[0155] In a first embodiment, a method is provided for mapping quality of service (QoS) flows to data radio bearers, the method comprising: determining, by a communication device, a data volume in a queue of a first DRB; and determining, by the communication device, that the data volume in the queue of the first DRB does not reach a specified threshold, and based thereon: mapping, by the communication device, the first QoS flow to the first data radio bearer; and transmitting, by the communication device, a packet of the first QoS flow over the first data radio bearer.
[0156] The method of the first embodiment may further include receiving, by the communication device, a QoS flow to data radio bearer mapping configuration for the first data radio bearer. The QoS flow to data radio bearer mapping configuration being received in a radio resource control (RRC) message.
[0157] The method of the first embodiment may further include determining, by the communication device, a data volume in a queue of a second data radio bearer; and determining, by the communication device, that the data volume in the queue of the second data radio bearer does not exceed the specified data threshold, and based thereon: mapping, by the communication device, the QoS flow to a second data radio bearer; and transmitting, by the communication device, a packet of the QoS flow over the second data radio bearer.
[0158] In the method of the first embodiment, the communication device is a user equipment (UE). In the method of the first embodiment, mapping the first QoS flow to the first data radio bearers is performed by a service data application protocol (SDAP) entity of the communication device. [0159] In a second embodiment, a method is provided for mapping quality of service (QoS) flows to data radio bearers, the method comprising: determining, by a communication device, a characteristic measure of a QoS flow and/or of a plurality of data radio bearers associated with the QoS flow; mapping, by the communication device, the QoS flow to one of the DRB in accordance with the characteristic measure of the QoS flow or of the DRBs; and transmitting, by the communication device, a packet of the QoS flow over the mapped data radio bearer.
[0160] The method of the second embodiment may further include receiving, by the communication device, a QoS flow to data radio bearer mapping configuration for the plurality of data radio bearers in a radio resource control (RRC) message.
[0161] In the method of the second embodiment, mapping the QoS flow to the one of the plurality of data radio bearers includes: determining, by the communication device, if the characteristic measure of the QoS flow is equal to or below a specified characteristic threshold; mapping, by the communication device, the QoS flow to a first data radio bearer in response to determining that the characteristic measure of the QoS flow is equal to or below the specified characteristic threshold; and mapping, by the communication device, the QoS flow to a second data radio bearer in response to determining that the characteristic measure of the QoS flow exceeds the specified characteristic threshold.
[0162] In the method of the second embodiment, the characteristic measure comprising at least one of a maximum data burst volume, a cumulative data rate, a cumulative delay, a cumulative packet error rate, a packet size, a packet type, a number of dropped packets, a buffer size, or a QoS parameter. In the method of the second embodiment, mapping the QoS flow to the one of the plurality of data radio bearers occurs dynamically.
[0163] In a third embodiment, a method for generating report of connection characteristics of quality of service (QoS) flows is provided, and the method includes: determining, by a communication device, a characteristic measure of data radio bearers (DRBs); and comparing, by the communication device, the characteristic measure of the DRBs with a specified threshold, and based thereon: generating, by the communication device, a report of connection characteristics of the QoS flows.
[0164] The method of the third embodiment further includes receiving, by the communication device, a reporting configuration for the connection characteristics of the QoS flows. In the method of the third embodiment, the reporting configuration is received in a radio resource control (RRC) message. In the method of the third embodiment, the communication device includes a user equipment (UE). In the method of the third embodiment, generating the report of connection characteristic of the QoS flow is performed by a service data application protocol (SDAP) entity of the communication device.
[0165] The method of the third embodiment further includes determining, by the communication device, a data volume of a queue of a DRB; and determining, by the communication device, that the data volume of the queue of the DRB is meets the specified threshold, and based thereon: generating, by the communication device, a queue size report for the report of connection characteristics.
[0166] The method of the third embodiment further includes determining, by the communication device, a data volume transmitted in a time duration of DRBs; and determining, by the communication device, that the data volume transmitted in the time duration of the DRBs meets the specified threshold, and based thereon: generating, by the communication device, a data rate report for the report of connection characteristics.
[0167] In a fourth embodiment, a device is provided that includes one or more processors, and a non-transitory memoiy storage including instructions that, when executed by the one or more processors, cause the device to perform the methods of the first embodiment, the second embodiment and the third embodiment.
[0168] An embodiment includes mapping a QoS flow to multiple DRBs, and determining dynamically which DRB(s) packets of the QoS flow should be delivered to. A maximum queue size may be configured for a DRB. Queue size is measured as the data volume in MAC/RLC/PDCP entities of a DRB, and it may be equivalent to the sum of buffer status of logical channels associated with the DRB. Packets of QoS flow are steered to DRB(s) according to their queue size, experienced data rate and reliability, etc.
[0169] While the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution described in the present disclosure may be embodied in the form of a software product. A suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitoiy computer readable medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example. The software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute embodiments of the methods disclosed herein.
[0170] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a mapping unit or module, a reporting unit or module, a packet generating unit or module, a packet to QoS flow mapping unit or module, a QoS flow to DRB mapping unit or module, a characteristic measure unit or module, a characteristic measure comparing unit or module, a report generating unit or module, a configuring unit or module, a signaling unit or module, and/or a determining unit or module. The respective units or modules may be hardware, software, or a combination thereof. For instance, one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).
[0171] Although this disclosure has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the disclosure, will be apparent to persons skilled in the art upon reference to the description. Selected features from one or more of the above-described embodiments may be combined to create alternative embodiments not explicitly described, features suitable for such combinations being understood within the scope of this disclosure. It is therefore intended that the appended claims encompass any such modifications or embodiments.

Claims

WHAT IS CLAIMED IS:
1. A method comprising: determining, by a communication device, a characteristic measure of a first data radio bearer (DRB); and when the characteristic measure of the first DRB satisfies a condition, mapping, by the communication device, a first data packet of a quality of service (QoS) flow to the first DRB; and transmitting, by the communication device, the first data packet over the first DRB.
2. The method of claim 1, further comprising: when the characteristic measure of the first DRB does not satisfy the condition, determining, by the communication device, whether to map the data packet of the QoS flow to a second DRB for transmission.
3. The method of claim 2, further comprising: determining, by the communication device, a characteristic measure of the second DRB.
4. The method of any one of claims 1-3, further comprising: determining, by the communication device, that a characteristic measure of a third DRB satisfies the condition; mapping, by the communication device, a second data packet of the QoS flow to the third DRB; and transmitting, by the communication device, the second data packet over the third DRB.
5. The method of any one of claims 1-4, wherein the characteristic measure of the first DRB, the second DRB or the third DRB comprises one of following: a data volume in a queue of a DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or
-37- a priority of the DRB.
6. The method of any one claims 1-5, further comprising: comparing, by the communication device, the characteristic measure of the first DRB with a threshold to determine whether the characteristic measure of the first DRB satisfies the condition.
7. The method of claim 6, wherein the condition specifies the characteristic measure of the first DRB and the threshold.
8. The method of any one claims 1-7, wherein the characteristic measure of the first DRB comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition.
9. The method of any one claims 1-8, wherein the characteristic measure of the first DRB is a sum or an average of values of the characteristic measure of the first DRB for a period of time.
10. The method of any one claims 1-9, wherein the communication device is a user equipment (UE).
11. The method of any one claims 1-10, further comprising: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
12. A method comprising : determining, by a communication device, a characteristic measure of data packets of a quality of service (QoS) flow; when the characteristic measure of the data packets satisfies a condition, mapping, by the communication device, a first data packet of the QoS flow to a first data radio bearer (DRB); and transmitting, by the communication device, the first data packet over the first DRB.
13. The method of claim 12, further comprising:
-38- when the characteristic measure of the data packets does not satisfy the condition, mapping, by the communication device, the first data packet of the QoS flow to a second DRB; and transmitting, by the communication device, the first data packet over the second DRB.
14. The method of any one of claims 12-13, wherein the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
15. The method of any one claims 12-14, further comprising: comparing, by the communication device, the characteristic measure of the data packets of the QoS flow with a threshold to determine whether the characteristic measure satisfies the condition.
16. The method of claim 15, wherein the condition specifies the characteristic measure and the threshold.
17. The method of any one claims 12-16, wherein the characteristic measure comprises a first measure and a second measure, and the condition is satisfied when the first measure satisfies a first condition and the second measure satisfies a second condition.
18. The method of any one claims 12-17, wherein the characteristic measure is a sum or an average of values of the characteristic measure of the packets of the QoS flow for a period of time.
19. The method of any one claims 12-18, wherein the communication device is a user equipment (UE).
20. The method of any one claims 12-19, further comprising: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for mapping QoS flows to DRBs, the configuration comprising the condition.
21. A method comprising: determining, by a communication device, a characteristic measure of a data radio bearers (DRB) or of packets of a quality of service (QoS) flow; when the characteristic measure satisfies a condition, generating, by the communication device, a report of transmission characteristics of one or more data packets of the QoS flow.
22. The method of claim 21, wherein the characteristic measure of the DRB comprises one of following: a data volume in a queue of the DRB; a data rate of the DRB; a maximum data burst volume (MDBV) supported by the DRB; a packet error rate of the DRB; a transmission delay of the DRB; packet waiting time of the DRB; an amount of data transmitted over the DRB in a time interval; time taken for successful transmission of a packet over the DRB; or a priority of the DRB.
23. The method of any one of claims 21-22, wherein the characteristic measure of the packets of the QoS flow comprises one of following: a data rate of the QoS flow; a maximum data burst volume (MDBV) of the QoS flow; a data volume of the QoS flow; a packet size of the QoS flow; a packet type of the QoS flow; packet waiting time of the QoS flow; a priority of the QoS flow; or a buffer size of the QoS flow.
24. The method of any one of claims 21-23, further comprising: comparing, by the communication device, the characteristic measure with a threshold to determine whether the characteristic measure satisfies the condition.
25. The method of claim 24, wherein the condition specifies the characteristic measure of the first DRB and the threshold.
26. The method of any one claims 21-25, wherein the report comprises one or more of following: a data rate; a transmission delay; a packet waiting time; a queue size; data transmitted in a time window; a number of packet errors in a time duration; time taken for successful packet transmission; or a packet dropping rate.
27. The method of any one claims 21-26, wherein the communication device is a user equipment (UE).
28. The method of any one claims 21-27, further comprising: receiving, by the communication device in a radio resource control (RRC) signaling, a configuration for generating the report, the configuration comprising the condition.
29. An apparatus comprising: a non-transitory memory storage comprising instructions; and one or more processors in communication with the memory storage, wherein the instructions, when executed by the one or more processors, cause the apparatus to perform a method of any one of claims 1-28.
30. A non-transitory computer-readable media storing computer instructions that when executed by one or more processors of an apparatus, cause the apparatus to perform a method of any one of claims 1-28.
PCT/US2022/032232 2021-06-04 2022-06-03 Methods and apparatus for communications over data radio bearer WO2022165447A2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163197165P 2021-06-04 2021-06-04
US202163197028P 2021-06-04 2021-06-04
US63/197,028 2021-06-04
US63/197,165 2021-06-04

Publications (2)

Publication Number Publication Date
WO2022165447A2 true WO2022165447A2 (en) 2022-08-04
WO2022165447A3 WO2022165447A3 (en) 2022-10-06

Family

ID=82483402

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/032232 WO2022165447A2 (en) 2021-06-04 2022-06-03 Methods and apparatus for communications over data radio bearer

Country Status (1)

Country Link
WO (1) WO2022165447A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024035697A1 (en) * 2022-08-08 2024-02-15 Apple Inc. Higher layer influence on qos flow to drb mapping

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102385420B1 (en) * 2017-06-15 2022-04-12 삼성전자 주식회사 Method and apparatus for reporting network requested buffer status report in next generation mobile communication system
US11184819B2 (en) * 2018-09-20 2021-11-23 Qualcomm Incorporated Avoiding out of order uplink data reception upon data radio bearer release, handover to another data radio bearer, or quality of service flow addition
CN114762387A (en) * 2019-11-06 2022-07-15 华为技术有限公司 Method and apparatus for mapping of data packet flows to data radio bearers

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024035697A1 (en) * 2022-08-08 2024-02-15 Apple Inc. Higher layer influence on qos flow to drb mapping

Also Published As

Publication number Publication date
WO2022165447A3 (en) 2022-10-06

Similar Documents

Publication Publication Date Title
EP3111578B1 (en) System and method for joint transmission over licensed and unlicensed bands using fountain codes
US10721754B2 (en) Data transmission method and apparatus
US20220182185A1 (en) Systems and Methods to Reduce Consecutive Packet Loss for Delay Critical Traffic
EP3874638B1 (en) Apparatus, method and computer program
US10291541B1 (en) Systems and methods for scheduling transmissions from an access node
CN107710817B (en) Joint Radio Link Control (RLC) signaling with network coding
US20220264359A1 (en) Methods and Apparatus for Packet Flow to Data Radio Bearer Mapping
US20210219171A1 (en) Communication method and device
WO2022165447A2 (en) Methods and apparatus for communications over data radio bearer
WO2015018009A1 (en) Method for automatic retransmission, user equipment, and base station
WO2017074362A1 (en) Multi-level data rate control for wireless networks
CN114073121B (en) Method and apparatus for flow control
EP3900461A1 (en) Apparatus, method and computer program
US20230262809A1 (en) Methods and Apparatus for Logical Channel Aggregation
JP2024064705A (en) Mobile communication system, server device, base station device, and core network device
JP2023524345A (en) Method and apparatus for signaling suspension and resumption of network coding operations
JP2024520661A (en) User equipment, scheduling node, method for user equipment, and method for scheduling node - Patents.com
WO2024081973A2 (en) Methods and apparatus for handling pdus to achieve target pdu set error rate in transmission
CN116762397A (en) Signal transmitting and receiving method, device and communication system
Manaz et al. Delay analysis of small IP packets in GPRS RLC layer

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22740627

Country of ref document: EP

Kind code of ref document: A2