WO2020128750A1

WO2020128750A1 - Reducing uplink scheduling latency and overhead for standard packet sizes

Info

Publication number: WO2020128750A1
Application number: PCT/IB2019/060774
Authority: WO
Inventors: Mads LAURIDSEN; Jeroen Wigard; István Z. KOVÁCS; Daniela Laselva
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2018-12-21
Filing date: 2019-12-13
Publication date: 2020-06-25
Also published as: EP3900455A1

Abstract

A method, apparatus, and a computer-readable storage medium are provided. In one example implementation, the method may include receiving logical channel group (LCG) mapping information from a network node, detecting presence of data for transmitting from the user equipment (UE) to the network node,; determining whether a size of the data matches a buffer size value indicated by at least one of the buffer status index (BSI) values, and selecting a logical channel group (LCG) associated with the at least one of the buffer status index (BSI) values The method may further include transmitting a scheduling request (SR) to the network node.

Description

REDUCING UPLINK SCHEDULING LATENCY AND OVERHEAD FOR

STANDARD PACKET SIZES

TECHNICAL FIELD

[0001]This description relates to wireless communications, and in particular, to data transmissions from a user equipment (UE) for similar packet sizes.

BACKGROUND

[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is an architecture that is being standardized by the 3rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E-UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments.

[0004] 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks. In addition, 5G is also targeted at the new emerging use cases in addition to mobile broadband. A goal of 5 G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G NR may also scale to efficiently connect the massive Internet of Things (IoT), and may offer new types of mission-critical services. Ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.

SUMMARY

[0005] A method, apparatus, and a computer-readable storage medium are provided. In one example implementation, the method may include receiving, by a user equipment (UE), logical channel group (FCG) mapping information from a network node, the mapping information associating one or more logical channel groups (FCGs) configured for the user equipment (UE) to corresponding buffer status index (BSI) values; detecting, by the user equipment (UE), presence of data for transmitting from the user equipment (UE) to the network node; determining, in response to the detecting, whether a size of the data matches a buffer size value indicated by at least one of the buffer status index (BSI) values; and selecting, in response to determining the matching, a logical channel group (LCG) associated with the at least one of the buffer status index (BSI) values. The method may further include transmitting a scheduling request (SR) to the network node, wherein the scheduling request (SR) includes: an identifier of the selected logical channel group (LCG), wherein the identifier indicates that the selected logical channel group (LCG) is associated with a buffer status index (BSI) value in the mapping information, and indicates that the user equipment (UE) is not requesting scheduling grant from the network node to transmit a buffer status report (BSR) for the data.

[0006] A method, apparatus, and a computer-readable storage medium are provided. In one example implementation, the method may include transmitting, by a network node, logical channel group (LCG) mapping information to a user equipment (UE), the mapping information associating one or more logical channel groups (LCGs) configured for the user equipment (UE) to corresponding buffer status index (BSI) values; receiving a scheduling request (SR) from the user equipment, wherein the scheduling request (SR) includes: an identifier of a logical channel group (LCG) selected by the user equipment (UE), wherein the identifier indicates whether the selected logical channel group (LCG) is associated with at least one of buffer status index (BSI) values in the mapping

information, and indicates whether the user equipment (UE) is requesting scheduling grant from the network node to transmit a buffer status report (BSR) for data from the user equipment (UE).

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a block diagram of a wireless network according to an example implementation.

[0008] FIG. 2 is a message flow diagram illustrating transmitting of a scheduling request from a UE to a network node, according to an example implementation.

[0009] FIG. 3 is a message flow diagram illustrating transmitting of a scheduling request from a UE to a network node, according to another additional example implementation.

[0010] FIG. 4 is a flow chart illustrating transmitting a scheduling request from a user equipment, according to an example implementation.

[0011]FIG. 5 is a block diagram of a node or wireless station (e.g., base station/access point or mobile station/user device/UE), according to an example implementation.

DETAILED DESCRIPTION

[0012] FIG. 1 is a block diagram of a wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB) or a network node. At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices 131, 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.

[0013] A user device (user terminal, user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples, or any other wireless device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.

[0014] In LTE (as an example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.

[0015] In addition, by way of illustrative example, the various example implementations or techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types. New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), Internet of Things (IoT), and/or narrowband IoT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC).

[0016] IoT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC or machine to machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans. Enhanced mobile broadband (eMBB) may support much higher data rates than currently available in LTE.

[0017] Ultra-reliable and low-latency communications (URLLC) is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems. This enables emerging new applications and services, such as industrial automations, autonomous driving, vehicular safety, e-health services, and so on. 3GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10-5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example. Thus, for example, URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency, as compared to a eMBB UE (or an eMBB application running on a UE).

[0018] The various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G, IoT, MTC, eMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies or data service types are provided only as illustrative examples.

[0019] Multiple Input, Multiple Output (MIMO) may refer to a technique for increasing the capacity of a radio link using multiple transmit and receive antennas to exploit multipath propagation. MIMO may include the use of multiple antennas at the transmitter and/or the receiver. MIMO may include a multi-dimensional approach that transmits and receives two or more unique data streams through one radio channel. Lor example,

MIMO may refer to a technique for sending and receiving more than one data signal simultaneously over the same radio channel by exploiting multipath propagation.

According to an illustrative example, multi-user multiple input, multiple output (multi user MIMIO, or MU-MIMO) enhances MIMO technology by allowing a base station (BS) or other wireless node to simultaneously transmit multiple streams to different user devices or UEs, which may include simultaneously transmitting a first stream to a first UE, and a second stream to a second UE, via a same (or common or shared) set of physical resource blocks (PRBs) (e.g., where each PRB may include a set of time- frequency resources). [0020] Also, a BS may use precoding to transmit data to a UE (based on a precoder matrix or precoder vector for the UE). For example, a UE may receive reference signals or pilot signals, and may determine a quantized version of a DL channel estimate, and then provide the BS with an indication of the quantized DL channel estimate. The BS may determine a precoder matrix based on the quantized channel estimate, where the precoder matrix may be used to focus or direct transmitted signal energy in the best channel direction for the UE. Also, each UE may use a decoder matrix may be determined, e.g., where the UE may receive reference signals from the BS, determine a channel estimate of the DL channel, and then determine a decoder matrix for the DL channel based on the DL channel estimate. For example, a precoder matrix may indicate antenna weights (e.g., an amplitude/gain and phase for each weight) to be applied to an antenna array of a transmitting wireless device. Likewise, a decoder matrix may indicate antenna weights (e.g., an amplitude/gain and phase for each weight) to be applied to an antenna array of a receiving wireless device.

[0021] For example, according to an example aspect, a receiving wireless user device may determine a precoder matrix using Interference Rejection Combining (IRC) in which the user device may receive reference signals (or other signals) from a number of BSs (e.g., and may measure a signal strength, signal power, or other signal parameter for a signal received from each BS), and may generate a decoder matrix that may suppress or reduce signals from one or more interferers (or interfering cells or BSs), e.g., by providing a null (or very low antenna gain) in the direction of the interfering signal, in order to increase a signal-to interference plus noise ratio (SINR) of a desired signal. In order to reduce the overall interference from a number of different interferers, a receiver may use, for example, a Linear Minimum Mean Square Error Interference Rejection Combining (LMMSE-IRC) receiver to determine a decoding matrix. The IRC receiver and LMMSE- IRC receiver are merely examples, and other types of receivers or techniques may be used to determine a decoder matrix. After the decoder matrix has been determined, the receiving UE/user device may apply antenna weights (e.g., each antenna weight including amplitude and phase) to a plurality of antennas at the receiving UE or device based on the decoder matrix. Similarly, a precoder matrix may include antenna weights that may be applied to antennas of a transmitting wireless device or node. [0022]The scheduling request (SR) procedure (e.g., a four-step procedure) may include the following: 1) UE triggers a buffer status report (BSR) and sends a SR for a buffer status report (BSR) to a gNB; 2) gNB sends uplink grants for sending the BSR; 3) UE sends the BSR to the gNB; and 4) gNB allocates uplink grants for transmitting the data reported in the BSR.

[0023]The procedure described above includes a long delay (e.g., 2 x round trip time; UE to gNB (e.g., satellite) and gNB (satellite) to UE) before the UE can transmit the data in the buffer on the uplink. For instance, in the case of geostationary (GEO) regenerative satellites (with full gNB on board the satellites), this delay can be, e.g., ~ 1.1 seconds (4 x 270 ms). For bent-pipe satellites transmissions, the delay can be ~ 2.2 seconds (4 x 540 ms). For low earth orbit (LEO) and medium earth orbit (MEO) satellites, the delay can be much smaller, but the delay is still significantly larger than the delay in terrestrial networks. Therefore, in non-terrestrial networks (NTNs) using New Radio (NR) or LTE, there is a desire to minimize the above described delays and improve network performance (e.g., reduce latency/signalling overhead, improve throughout, etc.).

[0024] In addition, in Internet of Things (IoT)/massive IOT deployments (e.g., factories, remote sensors, remote monitoring, etc.), messages transmitted (or exchanged) are typically using packets of same size (e.g., similar, almost same, etc.) for most of the time (e.g., majority of the time). For example, downloading of information (e.g., browsing, social media) by 4G/5G UEs is typically based on transmission control protocol (TCP) and the downlink TCP packets are acknowledged (ACK)with uplink TCP ACK packets of fixed size (e.g., 40 bytes in size). Although the packets on the uplink may be of different sizes, certain packet sizes are more frequent than others.

[0025] Therefore, the present disclosure proposes a procedure/mechanism that optimizes the above four-step scheduling procedure to reduce the overall user plane latency that the UE may experience. For example, in some implementations, the mechanism may include a two-step uplink procedure (instead of the four-step uplink scheduling procedure) when a UE has quasi-constant data packet size and irregular transmissions in time.

[0026] In one example implementation, the proposed disclosure describes a procedure that may include a network node transmitting logical channel group (LCG) mapping information to a user equipment (UE). The LCG mapping information associates (e.g., pre-maps) one or more LCGs configured for the UE to corresponding buffer size index (BSI) values. The UE, upon receiving the LCG mapping information, determines whether data size in a buffer at the UE matches a buffer size value indicated by at least one of the BSI values. The UE, if a match is determined, transmits a scheduling request (SR) to the network node indicating a selected LCG and that the UE is not requesting scheduling grant(s) from the network node to transmit a buffer status report (BSR).

[0027] FIG. 2 is a message flow diagram 200 illustrating transmitting of data from a UE to a network node, according to one example implementation.

[0028]At 212, a UE (e.g., UE 202) may receive logical channel group (LCG) mapping information from a network node (e.g., gNB 204).

[0029] In some implementations, the mapping information received by UE 202 (from gNB 204) may include LCGs configured for UE 202, including LCGs pre-mapped to BSI values, for example, as shown in Tables I and II below. The pre-mapping between LCGs and BSI values may also be considered as defining associations between LCGs and BSI values.

[0030]In an example implementation shown in Table I below, the LCG mapping information received by UE 202, from network node 204, may include four LCGs (e.g., LCGs 1, 2, 3, and 4). Out of the four LCGs, two LCGs (e.g., LCGs 1 and 2) may be considered as pre-mapped LCGs (e.g., LCGs 1 and 2 have associated BSI values defined by gNB 204) with BSI values 32 and 41, respectively. The BSI values may be based on Table 6.1.3.1-2 of TR 38.321 (or Table 6.1.3.1-1 of TR 36.321). As shown below in Table I, if a LCG does not have an associated BSI value, e.g., LCGs 3 and 4 of Table I, it means LCGs 3 and 4 are not pre-mapped, and normal LCG operations are used.

[0031]In addition, in Table 1, for example, a plurality of pre-mapped LCGs (e.g., LCGs 1 and 2 are configured for the same DRB (e.g., DRB 1) and LCGs 3 and 4 do not have pre-mapping (e.g., LCG-BSI mapping = none) and are configured for just one DRB,

DRBs 1 and 2, respectively. In some implementation, the buffer sizes and BSI values used for LCG-BSI mapping may be according to 3GPP Specifications. Table

[0032] In Release 15, only one LCG can be mapped per DRB. However, in the example implementation shown in Table I, three LCGs (e.g., LCGs 1, 2, and 3) are mapped to DRB 1. Therefore, the above described implementation (multiple LCGs per DRB) may require signalling changes. In other words, a DRB may be associated with only one regular LCG, but may be associated with one or more pre-mapped LCGs.

[0033] In an example implementation shown in Table II below, a DRB is associated with one LCG and two LCGs are pre-mapped. For example, LCGs 1 and 2 are pre-mapped and DRBs 1 and 2 are associated with LCGs 1 and 2, respectively.

Table

[0034] The LogicalChannelConfig Information Element (IE) is used to configure logical channel parameters. In some implementations, the LogicalChannelConfig IE may be used to convey the association between a LCG and a BSI value, via a new attribute (or field) in the LogicalChannelConfig IE. For example, the new attribute/field,“default BSI” may indicate the BSI associated with the LCG.

[0035] In some implementations, the mapping information may also include mapping of a data radio bearer (DRB) or a logical channel to a Logical Channel Group (LCG) at DRB setup time by the gNB based on the corresponding Quality of Service (QoS) attributes (e.g., QoS Class Identifier (QCI)/5QI) of the DRBs. In some more implementations, the association between LCG and BSI value, if configured, may be stored at UE and gNB, for example, as media access control (MAC) context information while a UE is in a

RRC_INACTIVE state. The stored information may be used when the UE transitions to RRC_CONNECTED state, for instance, until a RRC reconfiguration message is received.

[0036] For example, in some implementations, UE 202 may receive the mapping information as part of an Information Element (IE) (e.g., LogicalChannelConfig IE) from gNB 204. The IE may be received via a radio resource control (RRC) configuration or RRC reconfiguration message.

[0037] At 214, UE 202 may configure LCG and/or LCG-BSI associations at the UE, for example, based on the LCG mapping information, received from gNB 204. At 216, UE 202 may detect the presence of data for transmitting from UE 202 to gNB 204. The data may be present in a buffer (e.g., packet data convergence protocol (PDCP) or media access control (MAC) buffer) at the UE.

[0038] At 218, UE 202 may determine that the size of the data present in the buffer matches a buffer size (BS) value associated with a BSI value that is pre-mapped to a LCG. In other words, UE 202 may determine that the buffer size matches a buffer size value indicated by at least one of the BSI values. In an example implementation, if the size of the data present in a buffer at UE 202 is 1200 bytes, UE 202 may determine the size of the data present in the buffer at UE 202 matches a BSI value of 32 which is associated with LCG 1 (based on pre-mapping). In another example, if the size of the data present in a buffer at UE 202 is 5000 bytes, UE 202 may determine the size of the data present in the buffer at UE 202 matches a BSI value of 41 which is associated with LCG 2 (based on pre-mapping). At 220, UE 202, UE may select LCG 1 (or LCG 2) based on the matched BSI value.

[0039]At 222, UE 202 may send a scheduling request (SR) for data. In some

implementations, when UE 202 selects a LCG based on a matched BSI value, the SR may include an identifier of the selected logical channel group (LCG), for example, LCG 1 or LCG 2. In an example implementation, the identifier (included in the SR) indicates that the selected logical channel group (LCG) is associated with a buffer status index (BSI) value in the mapping information. This (indication) is used by network node 204 to determine the BSI value for further determining the uplink grants to be allocated to UE 202 for transmitting the data (in the buffers) from the UE. In addition, the indication indicates that the user equipment (UE) is not requesting scheduling grants from the network node to transmit a buffer status report (BSR) for the data. In other words, the indication indicates to gNB 204 that UE 202 is using the enhanced mechanism and that there is no need to transmit the BSR to gNB 202 (and which means there is no need to assign uplink grants to UE 202 to transmit the BSR).

[0040] On the receiving end, for example, gNB 204, in some implementations interprets the reporting of LCG 1 as being associated with a BSI value of 32 (as gNB configured the association(s) between LCG and BSI value) and allocates resources (e.g., uplink grants) to UE 202 accordingly. In other words, gNB 204 may allocate uplink grant resources needed to transmit data present in the buffer at the UE, for example, to transmit about 1132-1326 bytes (e.g., based on BSI value of 32). Similarly, in some implementations, on the receiving end at gNB 204, the gNB may interpret the reporting of LCG 2 as being associated with a BSI value of 41 and allocate resources (e.g., uplink grants) to UE 202 accordingly. In other words, gNB 204 may allocate uplink grant resources needed to transmit data present in the buffer at the UE, for example, to transmit about 4677-5476 bytes.

[0041]At 224, UE 202 receives scheduling grants from gNB 204 and transmit the data from UE 202 to the network node 204.

[0042]Thus, the association (or pre-mapping) of LCGs and BSI values and including such association (or pre-mapping) in the LCG mapping information sent from a gNB to a UE allows the four-step SR procedure to be reduced to (or improved, enhanced, optimized) two steps as described above, for example, when the UE transmits packets of mostly (e.g., majority) standard (e.g., similar, same) size to reduce latency and/or overhead in the network. The above described procedure may be used in, for example,

IoT, non-terrestrial communications, etc.

[0043] FIG. 3 is a message flow diagram 300 illustrating transmitting of data from a UE to a network node, according to an additional example implementation.

[0044]In some implementations, for example, operations at 312, 314, and 316 of FIG. 3 may be same/similar to operations 212, 214, and 216 of FIG. 2, respectively.

[0045]At 328, UE 202 may determine that the size of the data in the buffer does not match (e.g., fails to match) a buffer size value of the BSI values. In such a scenario, UE 202 may not select one of the pre-mapped LCGs and may instead use the four-step SR procedure, described above, as a fallback procedure.

[0046] For example, if UE 202 determines that the size of the data present in a buffer at UE 202 is 2500 bytes, UE 202 may determine that the size of the data present in the buffer at UE 202 does not match (fails to match) a BSI value which is associated with a pre mapped LCG. Since LCGs 3 and 4 are configured for normal operations (e.g., not pre mapped), at 330, UE 202 may trigger a buffer status report (BS) and send a scheduling request to gNB 204. The SR transmitted at 330 is requesting the gNB for uplink grants for transmitting the BSR.

[0047] At 332, UE 202 receives scheduling grants from gNB 204 for transmitting the BSR to gNB 204. At 334, UE 202 sends the BSR to gNB 204 using the uplink grants received from gNB 204. In some implementations, for example, the BSR includes, at least, a buffer size value (e.g., amount of data in the buffers at UE 202) so that gNB 204 can provide uplink grants accordingly for transmitting the data present in the buffer(s) at UE 202. At 336, UE 202 receives scheduling grants (e.g., uplink grants) to transmit the data on the uplink to gNB 204.

[0048]In some implementations, the SR sent from UE 202, at 330, may include an indication (e.g., a flag) which indicates that the UE is using the four-step procedure. In other words, the indication may indicate to gNB 204 that the UE 202 will require uplink grant resources for transmitting a BSR. In one example implementation, the indicator may be in the form of a flag that is set to try to indicate to gNB 204 that the SR is associated with a SR for BSR and indicating to gNB 204 that the gNB needs to allocate uplink grants to UE 202 for transmitting the BSR. In other words, the use of the indicator (or flag) functions as an explicit indicator to gNB 204 on whether UE 202 is using the enhanced SR procedure.

[0049]Thus, a UE may try to send a SR with a pre-mapped LCG to obtain uplink grants for transmitting data to a gNB. However, if one of the pre-mapped LCGs cannot be used (e.g., no data size match to pre-mapped BSI value), UE 202 may send a SR, using the LCGs that are not pre-mapped (e.g., using the four-step SR procedure).

[0050]In some implementations, the advantages of the above described procedures include: i) reducing uplink scheduling latency is reduced when most of the expected data traffic (U-plane) contains quasi-constant packet size, with potentially irregular arrival times; ii) transmitting data packets with sizes that are significantly different than the pre mapped values is possible with fallback to regular uplink SR procedure (e.g., four-step SR procedure, including BSR); iii) reducing UL/DL signalling (C-plane) for executing UL data scheduling; and/or iv) provide a more flexible alternative to semi-persistent scheduling (SPS) where regular packet size and packet transmission rate is expected. The above described procedures reduce latency, improve performance, and/or reduce power consumption at the UE. In some implementations, the UE can transition to

RRC_INACTIVE state earlier than before once data transmission is successful.

[0051] FIG. 4 is a flow chart 400 illustrating a method of transmitting data from a user equipment (UE), for example, for similar or fixed packet sizes, according to at least one example implementation.

[0052]At block 410, a UE (e.g., UE 202) may receive a LCG mapping information from a network node (e.g., gNB 204). In some implementations, the mapping information may associate LCGs to BSI values. In other words, gNB 204 may pre-map some of the LCGs included in the LCG mapping information to BSI values, as described above. The pre mapping/association between LCG and BSI values may be of: one-to-one or many-to-one.

[0053] At block 420, the UE may detect the presence of data for transmitting from the UE to the network node. For example, in some implementations, UE 202 may detect the presence of data, e.g., in PDCP or MAC buffers at UE 202, for transmitting on the uplink to gNB 204.

[0054] At block 430, the UE may determine whether a size of the data matches a buffer size value indicated by at least one of the pre-mapped buffer status index (BSI) values.

For example, in some implementation, UE 202 may determine whether the size of the data in the buffer (e.g., buffer size (BS)) matches a buffer size value of at least one of the pre mapped BSI values. In other words, UE 202 determines whether there is a match so that the UE can determine whether the UE can use a pre-mapped LCG.

[0055] At block 440, the UE may select a logical channel group (LCG) associated with at least one of the buffer status index (BSI) values. For example, in some implementations, UE 202 may select the LCG associated with the match BSI value in response to determining that the size of the data matches a buffer size value of the one or more buffer status index (BSI) values.

[0056] At block 450, the may UE transmit a scheduling request (SR) to the user equipment. For example, in some implementations, UE 202 may transmit the SR to gNB 204.

[0057]Thus, as described above, a UE may transmit data to a gNB using the pre mapping between LCGs and BSI values, for example, to reduce latency, signalling data, power usage, etc.

[0058]Example 1. A method, comprising: receiving, by a user equipment (UE), logical channel group (LCG) mapping information from a network node, the mapping

information associating one or more logical channel groups (LCGs) configured for the user equipment (UE) to corresponding one or more buffer status index (BSI) values;

detecting, by the user equipment (UE), presence of data for transmitting from the user equipment (UE) to the network node; determining, in response to the detecting, whether a size of the data matches a buffer size value indicated by at least one of the one or more buffer status index (BSI) values; selecting, in response to determining the matching, a logical channel group (LCG) associated with the at least one of the one or more buffer status index (BSI) values; and transmitting a scheduling request (SR) to the network node, wherein the scheduling request (SR) includes an identifier of the selected logical channel group (LCG), wherein the identifier indicates that the selected logical channel group (LCG) is associated with a buffer status index (BSI) value in the mapping information, and the scheduling request (SR) indicates that the user equipment (UE) is not requesting scheduling grant from the network node to transmit a buffer status report (BSR) for the data.

[0059]Example 2. According to an example aspect of the method of Example 1, further comprising: receiving, from the network node, based on the identifier of the selected logical channel group (LCG) in the scheduling request (SR), scheduling grant for transmitting the data.

[0060] Example 3. According to an example aspect of the method of Example 1, further comprising: transmitting, in response to determining that the size of the data does not match a buffer size value indicated by at least one of the one or more buffer status index (BSI) values, a scheduling request (SR) to the network node, wherein the scheduling request (SR) requests a scheduling grant from the network node for transmitting a buffer status report (BSR).

[0061]Example 4. According to an example aspect of the method of Example 3, wherein the scheduling request (SR) further comprises a flag to indicate that the user equipment (UE) will be transmitting the buffer status report (BSR).

[0062] Example 5. According to an example aspect of the method of Example 3 or 4, wherein transmitting the scheduling request (SR) comprises: transmitting the scheduling request (SR) using a logical channel group (LCG) that is not associated with the buffer status index (BSI) values in the mapping information received from the network node.

[0063]Example 6. According to an example aspect of the method of Example 1 or 2, wherein the scheduling request (SR) includes a flag to indicate that the user equipment (UE) will not be transmitting the buffer status report (BSR).

[0064] Example 7. According to an example aspect of the method of any one of Examples 1 through 6, wherein the one or more buffer status index (BSI) values are indicated by the user equipment (UE) to the network node or suggested by the user equipment (UE) to the network node.

[0065] Example 8. According to an example aspect of the method of any one of\ Examples 1 through 7, wherein the mapping information is based on one or more of: an application or traffic profile at the user equipment (UE); Internet Protocol (IP) port number at the user equipment (UE); and media access control (MAC) address of the user equipment (UE).

[0066] Example 9. According to an example aspect of the method of any one of Examples 1 through 8, wherein the mapping information is received via a radio resource control (RRC) configuration or radio resource control (RRC) reconfiguration message.

[0067] Example 10. According to an example aspect of the method of any one of Examples 1 through 9, wherein the mapping information is received via an information element (IE) that includes configuration or reconfiguration information for any logical channel group (LCG). [0068] Example 11. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of examples 1-10.

[0069] Example 12. An apparatus comprising means for performing a method of any of examples 1-10.

[0070] Example 13. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform the steps of any of examples 1-10.

[0071]Example 14. A method, comprising: transmitting, by a network node, logical channel group (LCG) mapping information to a user equipment (UE), the mapping information associating one or more logical channel groups (LCGs) configured for the user equipment (UE) to corresponding one or more buffer status index (BSI) values; receiving a scheduling request (SR) from the user equipment, wherein the scheduling request (SR) includes an identifier of a logical channel group (LCG) selected by the user equipment (UE), wherein the identifier indicates whether the selected logical channel group (LCG) is associated with at least one of the one or more buffer status index (BSI) values in the mapping information, and the scheduling request (SR) indicates whether the user equipment (UE) is requesting scheduling grant from the network node to transmit a buffer status report (BSR) for data transmission from the user equipment (UE).

[0072]Example 15. According to an example aspect of the method of Example 14, wherein the identifier indicates that the selected logical channel group (LCG) is associated with at least one of the one or more buffer status index (BSI) values in the mapping information when a size of the data transmission from the user equipment (UE) matches a buffer size value indicated by the at least one of the one or more buffer status index (BSI) values in the mapping information, and wherein the indication indicates that the user equipment (UE) is not requesting scheduling grant from the network node to transmit a buffer status report (BSR) for the data from the user equipment (UE).

[0073]Example 16. According to an example aspect of the method of Example 14, wherein the identifier indicates that the selected logical channel group (LCG) is not associated with a buffer status index (BSI) value in the mapping information when a size of the data for transmitting from the user equipment (UE) fails to match a buffer size value indicated by the at least one of the one or more buffer status index (BSI) values in the mapping information, and wherein the indication indicates that the user equipment (UE) is requesting a scheduling grant from the network node to transmit a buffer status report (BSR) for the data transmission from the user equipment (UE).

[0074] Example 17. According to an example aspect of the method of any one of Examples 14 through 16, further comprising: granting, based on the identifier of the selected logical channel group (LCG) in the scheduling request (SR), a scheduling grant to the user equipment (UE).

[0075]Example 18. According to an example aspect of the method of any one of Examples 14 through 17, wherein the one or more buffer status index (BSI) values are indicated from the user equipment (UE) to the network node or suggested from the user equipment (UE) to the network node.

[0076]Example 19. According to an example aspect of the method of any one of Examples 14 through 18, wherein the mapping information is based on one or more of: an application or traffic profile at the user equipment (UE); Internet Protocol (IP) port number at the user equipment (UE); and media access control (MAC) address of the user equipment (UE).

[0077] Example 20. According to an example aspect of the method of any one of Examples 14 through 19, wherein the mapping information is transmitted via a radio resource control (RRC) configuration or radio resource control (RRC) reconfiguration message.

[0078]Example 21. According to an example aspect of the method of Example 20, wherein the mapping information is transmitted via an information element (IE) that includes configuration or reconfiguration information for any logical channel group (LCG).

[0079] Example 22. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of examples 14-21.

[0080] Example 23. An apparatus comprising means for performing a method of any of examples 14-21.

[0081]Example 24. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform the steps of any of examples 14-21.

[0082]FIG. 5 is a block diagram of a wireless station (e.g., user equipment (UE)/user device or AP/gNB) 500 according to an example implementation. The wireless station 500 may include, for example, one or more RF (radio frequency) or wireless transceivers 502A, 502B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 508 to execute instructions or software and control transmission and receptions of signals, and a memory 506 to store data and/or instructions.

[0083] Processor 504 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 504, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 502 (502A or 502B). Processor 504 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down- converted by wireless transceiver 502A/502B, for example). Processor 504 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 504 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 504 and transceiver 502A/502B together may be considered as a wireless transmitter/receiver system, for example.

[0084]In addition, referring to FIG. 5, a controller (or processor) 508 may execute software and instructions, and may provide overall control for the station 500, and may provide control for other systems not shown in FIG. 5, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 500, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[0085] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 504, or other controller or processor, performing one or more of the functions or tasks described above.

[0086] According to another example implementation, RF or wireless transceiver(s) 502A/502B may receive signals or data and/or transmit or send signals or data. Processor 504 (and possibly transceivers 502A/502B) may control the RF or wireless transceiver 502A or 502B to receive, send, broadcast or transmit signals or data.

[0087] The aspects are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[0088] It should be appreciated that future networks will most probably utilize network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into“building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[0089] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type

communications (MTC), and also via an Internet of Things (IOT).

[0090] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.

[0091]Furthermore, implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems.

Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.

[0092] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0093] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0094] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

Claims

CLAIMS:

1. A method, comprising:

receiving, by a user equipment, logical channel group mapping information from a network node, the mapping information associating one or more logical channel groups configured for the user equipment to corresponding one or more buffer status index values;

detecting, by the user equipment, presence of data for transmitting from the user equipment to the network node;

determining, in response to the detecting, whether a size of the data matches a buffer size value indicated by at least one of the one or more buffer status index values;

selecting, in response to determining the matching, a logical channel group associated with the at least one of the one or more buffer status index values; and

transmitting a scheduling request to the network node,

wherein the scheduling request includes an identifier of the selected logical channel group,

wherein the identifier indicates that the selected logical channel group is associated with a buffer status index value in the mapping information, and the scheduling request indicates that the user equipment is not requesting scheduling grant from the network node to transmit a buffer status report for the data.

2. A method of claim 1, further comprising: receiving, from the network node, based on the identifier of the selected logical channel group in the scheduling request, scheduling grant for transmitting the data.

3. A method of claim 1, further comprising: transmitting, in response to determining that the size of the data does not match a buffer size value indicated by at least one of the one or more buffer status index values, a scheduling request to the network node, wherein the scheduling request requests a scheduling grant from the network node for transmitting a buffer status report.

4. A method of claim 3, wherein the scheduling request further comprises a flag to indicate that the user equipment will be transmitting the buffer status report.

5. A method of claim 3 or claim 4, wherein transmitting the scheduling request comprises: transmitting the scheduling request using a logical channel group that is not associated with the buffer status index values in the mapping information received from the network node.

6. A method of claim 1 or claim 2, wherein the scheduling request includes a flag to indicate that the user equipment will not be transmitting the buffer status report.

7. A method of any of claims 1 through 6, wherein the one or more buffer status index values are indicated by the user equipment to the network node or suggested by the user equipment to the network node.

8. A method of any of claims 1 through 7, wherein the mapping information is based on at least one of: an application or traffic profile at the user equipment, Internet Protocol port number at the user equipment, or media access control address of the user equipment.

9. A method of any of claims 1 through 8, wherein the mapping information is received via a radio resource control configuration or radio resource control

reconfiguration message.

10. A method of any of claims 1 through 9, wherein the mapping information is received via an information element that includes configuration or reconfiguration information for any logical channel group.

11. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of claims 1 through 10.

12. An apparatus comprising means for performing a method of any of claims 1 through 10.

13. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform the steps of any of claims 1 through 10.

14. An apparatus comprising:

at least one processor; and

at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform:

receiving logical channel group mapping information from a network node, the mapping information associating one or more logical channel groups configured for the apparatus to corresponding one or more buffer status index values;

detecting presence of data for transmitting from the apparatus to the network node; determining, in response to the detecting, whether a size of the data matches a buffer size value indicated by at least one of the one or more buffer status index values;

selecting, in response to determining the matching, a logical channel group associated with the at least one of the one or more buffer status index values; and transmitting a scheduling request to the network node,

wherein the identifier indicates that the selected logical channel group is associated with a buffer status index value in the mapping information, and the scheduling request indicates that the apparatus is not requesting scheduling grant from the network node to transmit a buffer status report for the data.

15. An apparatus comprising means for performing:

detecting presence of data for transmitting to the network node;

16. A method, comprising:

transmitting, by a network node, logical channel group mapping information to a user equipment, the mapping information associating one or more logical channel groups configured for the user equipment to corresponding one or more buffer status index values; and

receiving a scheduling request from the user equipment,

wherein the scheduling request includes an identifier of a selected logical channel group from the user equipment,

wherein the identifier indicates whether the selected logical channel group is associated with at least one of the one or more buffer status index values in the mapping information, and the scheduling request indicates whether scheduling grant from the network node is requested for transmission of a buffer status report for data transmission from the user equipment.

17. A method of claim 16, wherein the identifier indicates that the selected logical channel group is associated with at least one of the one or more buffer status index values in the mapping information when a size of the data transmission from the user equipment matches a buffer size value indicated by the at least one of the one or more buffer status index values in the mapping information, and wherein the indication indicates that scheduling grant from the network node is not requested for transmission of a buffer status report for the data from the user equipment.

18. A method of claim 16, wherein the identifier indicates that the selected logical channel group is not associated with a buffer status index value in the mapping information when a size of the data transmission from the user equipment fails to match a buffer size value indicated by the at least one of the one or more buffer status index values in the mapping information, and wherein the indication indicates that scheduling grant from the network node is not requested for transmission of a buffer status report for the data transmission from the user equipment.

19. A method of any of claims 16 through 18, further comprising: granting, based on the identifier of the selected logical channel group in the scheduling request, a scheduling grant to the user equipment.

20. A method of any of claims 16 through 19, wherein the one or more buffer status index values are indicated from the user equipment to the network node or suggested from the user equipment to the network node.

21. A method of any of claims 16 through 20, wherein the mapping information is based on at least one of: an application or traffic profile at the user equipment, Internet Protocol port number at the user equipment, or media access control address of the user equipment.

22. A method of any of claims 16 through 21, wherein the mapping information is transmitted via a radio resource control configuration or radio resource control reconfiguration message.

23. A method of claim 22, wherein the mapping information is transmitted via an information element that includes configuration or reconfiguration information for any logical channel group.

24. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of claims 16 through 23.

25. An apparatus comprising means for performing a method of any of claims 16 through 23.

26. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform the steps of any of claims 16 through 23.

27. An apparatus comprising:

at least one processor; and

transmitting logical channel group mapping information to a user equipment, the mapping information associating one or more logical channel groups configured for the user equipment to corresponding one or more buffer status index values; and

receiving a scheduling request from the user equipment,

wherein the identifier indicates whether the selected logical channel group is associated with at least one of the one or more buffer status index values in the mapping information, and the scheduling request indicates whether scheduling grant from the apparatus is requested for transmission of a buffer status report for data transmission from the user equipment.

28. An apparatus comprising means for performing:

receiving a scheduling request from the user equipment,

wherein the identifier indicates whether the selected logical channel group is associated with at least one of the one or more buffer status index values in the mapping

information, and the scheduling request indicates whether scheduling grant from the apparatus is requested for transmission of a buffer status report for data transmission from the user equipment.