The present disclosure relates to communications devices, infrastructure equipment and methods for the more efficient operation of a communications device in a wireless communications network.
The present application claims the Paris Convention priority from European patent application number EP22153309.4, filed on 25 Jan. 2022, the contents of which are hereby incorporated by reference.
The “background” description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description which may not otherwise qualify as prior art at the time of filing, are neither expressly or impliedly admitted as prior art against the present invention.
Previous generation mobile telecommunication systems, such as those based on the 3GPP defined UMTS and Long Term Evolution (LTE) architecture, are able to support a wider range of services than simple voice and messaging services offered by previous generations of mobile telecommunication systems. For example, with the improved radio interface and enhanced data rates provided by LTE systems, a user is able to enjoy high data rate applications such as mobile video streaming and mobile video conferencing that would previously only have been available via a fixed line data connection. The demand to deploy such networks is therefore strong and the coverage area of these networks, i.e. geographic locations where access to the networks is possible, is expected to continue to increase rapidly.
Current and future wireless communications networks are expected to routinely and efficiently support communications with an ever-increasing range of devices associated with a wider range of data traffic profiles and types than existing systems are optimised to support. For example, it is expected future wireless communications networks will be expected to efficiently support communications with devices including reduced complexity devices, machine type communication (MTC) devices, high resolution video displays, virtual reality headsets, extended Reality (XR) and so on. Some of these different types of devices may be deployed in very large numbers, for example low complexity devices for supporting the “The Internet of Things”, and may typically be associated with the transmissions of relatively small amounts of data with relatively high latency tolerance. Other types of device, for example supporting high-definition video streaming, may be associated with transmissions of relatively large amounts of data with relatively low latency tolerance. Other types of device, for example used for autonomous vehicle communications and for other critical applications, may be characterised by data that should be transmitted through the network with low latency and high reliability. A single device type might also be associated with different traffic profiles/characteristics depending on the application(s) it is running. For example, different consideration may apply for efficiently supporting data exchange with a smartphone when it is running a video streaming application (high downlink data) as compared to when it is running an Internet browsing application (sporadic uplink and downlink data) or being used for voice communications by an emergency responder in an emergency scenario (data subject to stringent reliability and latency requirements).
In view of this there is expected to be a desire for current future wireless communications networks, for example those which may be referred to as 5G or new radio (NR) systems/new radio access technology (RAT) systems or indeed future 6G wireless communications, as well as future iterations/releases of existing systems, to efficiently support connectivity for a wide range of devices associated with different applications and different characteristic data traffic profiles and requirements.
One example of a new service is referred to as Ultra Reliable Low Latency Communications (URLLC) services which, as its name suggests, requires that a data unit or packet be communicated with a high reliability and with a low communications delay. URLLC type services therefore represent a challenging example for both LTE type communications systems and 5G/NR communications systems, as well as future generation communications systems.
The increasing use of different types of network infrastructure equipment and terminal devices associated with different traffic profiles give rise to new challenges for efficiently handling communications in wireless communications systems that need to be addressed.
The present disclosure can help address or mitigate at least some of the issues discussed above.
Embodiments of the present technique can provide a method of operating a communications device configured to transmit signals to and/or to receive signals from a wireless communications network via a wireless radio interface provided by the wireless communications network. The method comprises determining that the communications device has uplink data to transmit to the wireless communications network, and determining, independently from the wireless communications network, whether the communications device is to operate in accordance with a communications device based scheduling mode in order to transmit the uplink data. If the communications device determines that it is to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data, the method comprises, as the communications device based scheduling mode, switching from a first bandwidth part, BWP, of the wireless radio interface to a second BWP of the wireless radio interface for transmission of the uplink data, wherein the second BWP has a greater bandwidth than the first BWP and comprises a control resource and a data resource, transmitting, to the wireless communications network within the control resource, scheduling information indicating that the communications device is to transmit at least part of the uplink data to the wireless communications network, and transmitting, to the wireless communications network within the data resource, the at least part of the uplink data in accordance with the transmitted scheduling information.
Embodiments of the present technique, which, in addition to methods of operating communications devices, relate to methods of operating infrastructure equipment, communications devices and infrastructure equipment, circuitry for communications devices and infrastructure equipment, wireless communications systems, computer programs, and computer-readable storage mediums, can allow for more efficient use of radio resources by a communications device operating in a wireless communications network.
Respective aspects and features of the present disclosure are defined in the appended claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary, but are not restrictive, of the present technology. The described embodiments, together with further advantages, will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings.
A more complete appreciation of the disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings wherein like reference numerals designate identical or corresponding parts throughout the several views, and wherein:
The network 6 includes a plurality of base stations 1 connected to a core network 2. Each base station provides a coverage area 3 (i.e. a cell) within which data can be communicated to and from communications devices 4. Although each base station 1 is shown in
Data is transmitted from base stations 1 to communications devices 4 within their respective coverage areas 3 via a radio downlink. Data is transmitted from communications devices 4 to the base stations 1 via a radio uplink. The core network 2 routes data to and from the communications devices 4 via the respective base stations 1 and provides functions such as authentication, mobility management, charging and so on. Terminal devices may also be referred to as mobile stations, user equipment (UE), user terminal, mobile radio, communications device, and so forth. Services provided by the core network 2 may include connectivity to the internet or to external telephony services. The core network 2 may further track the location of the communications devices 4 so that it can efficiently contact (i.e. page) the communications devices 4 for transmitting downlink data towards the communications devices 4.
Base stations, which are an example of network infrastructure equipment, may also be referred to as transceiver stations, nodeBs, e-nodeBs, eNB, g-nodeBs, gNB and so forth. In this regard different terminology is often associated with different generations of wireless telecommunications systems for elements providing broadly comparable functionality. However, certain embodiments of the disclosure may be equally implemented in different generations of wireless telecommunications systems, and for simplicity certain terminology may be used regardless of the underlying network architecture. That is to say, the use of a specific term in relation to certain example implementations is not intended to indicate these implementations are limited to a certain generation of network that may be most associated with that particular terminology.
An example configuration of a wireless communications network which uses some of the terminology proposed for and used in NR and 5G is shown in
The elements of the wireless access network shown in
The TRPs 10 of
In terms of broad top-level functionality, the core network 20 connected to the new RAT telecommunications system represented in
It will further be appreciated that
Thus, certain embodiments of the disclosure as discussed herein may be implemented in wireless telecommunication systems/networks according to various different architectures, such as the example architectures shown in
A more detailed diagram of some of the components of the network shown in
The transmitters 30, 49 and the receivers 32, 48 (as well as other transmitters, receivers and transceivers described in relation to examples and embodiments of the present disclosure) may include radio frequency filters and amplifiers as well as signal processing components and devices in order to transmit and receive radio signals in accordance for example with the 5G/NR standard. The controllers 34, 44 (as well as other controllers described in relation to examples and embodiments of the present disclosure) may be, for example, a microprocessor, a CPU, or a dedicated chipset, etc., configured to carry out instructions which are stored on a computer readable medium, such as a non-volatile memory. The processing steps described herein may be carried out by, for example, a microprocessor in conjunction with a random access memory, operating according to instructions stored on a computer readable medium. The transmitters, the receivers and the controllers are schematically shown in
As shown in
The interface 46 between the DU 42 and the CU 40 is known as the F1 interface which can be a physical or a logical interface. The F1 interface 46 between CU and DU may operate in accordance with specifications 3GPP TS 38.470 and 3GPP TS 38.473, and may be formed from a fibre optic or other wired or wireless high bandwidth connection. In one example the connection 16 from the TRP 10 to the DU 42 is via fibre optic. The connection between a TRP 10 and the core network 20 can be generally referred to as a backhaul, which comprises the interface 16 from the network interface 50 of the TRP10 to the DU 42 and the F1 interface 46 from the DU 42 to the CU 40.
URLLC and eURLLC
Systems incorporating NR technology are expected to support different services (or types of services), which may be characterised by different requirements for latency, data rate and/or reliability. For example, Enhanced Mobile Broadband (eMBB) services are characterised by high capacity with a requirement to support up to 20 Gb/s. The requirements for Ultra Reliable and Low Latency Communications (URLLC) services are for one transmission of a 32 byte packet to be transmitted from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface within 1 ms with a reliability of 1-10−5 (99.999%) or higher (99.9999%) [2].
Massive Machine Type Communications (mMTC) is another example of a service which may be supported by NR-based communications networks. In addition, systems may be expected to support further enhancements related to Industrial Internet of Things (IIoT) in order to support services with new requirements of high availability, high reliability, low latency, and in some cases, high-accuracy positioning.
Enhanced URLLC (eURLLC) [3] specifies features that require high reliability and low latency, such as factory automation, transport industry, electrical power distribution, etc. in a 5G system. eURLLC is further enhanced as IIoT-URLLC [4], for which one of the objectives is to enhance UE feedback for Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) for Physical Downlink Shared Channel (PDSCH) transmissions.
As described above, several generations of mobile communications have been standardised globally up to now, where each generation took approximately a decade from introduction before the development and introduction of another new generation. For example, generations of mobile communications have moved from the Global System for Mobile Communications (GSM) (2G) to Wideband Code Division Multiple Access (WCDMA) (3G), from WCDMA (3G) to LTE (4G), and most recently from LTE (4G) to NR (5G).
The latest generation of mobile communications is 5G, as discussed above with reference to the example configurations of
Nevertheless, as in every decade, a new generation (e.g. 6G) is expected to be developed and deployed in the near future (around the year 2030), and will be expected to provide new services and capabilities that the current 5G cannot provide.
One of the areas for investigation for future mobile communications networks is uplink (UL) scheduling enhancements, which are expected to be required due to the increased number of services that require low latency communications and high reliability, as well as high throughput UL data transmissions from the terminal, like tactile internet, Audio-Video field production, and extended Reality (XR). In essence, it is proposed that a mobile terminal should be able to schedule unrestricted UL resources immediately after data arrives in its buffer for transmission, while taking into account the link adaptation parameters so that the transmissions are mostly ensured to be successful.
A typical use case (e.g. for broadcast TV production) is a camera transmitting a video stream using the User Data Protocol (UDP)/Internet Protocol (IP) protocol stack. In layer 2 of this protocol stack (L2), Radio Link Control-Unacknowledged Mode (RLC-UM) mode will be configured for UDP. Accordingly, dedicated (and probably regular) resources may be configured by the network, using techniques like periodic UL grant or configured grant. Such techniques are already developed and available.
As an example scenario, there might be a video algorithm which requires a camera not to transmit any uplink video frames if the view does not change. But as soon as the view changes, video codecs will have data available for transmission in L2 buffers. If traditional techniques are relied upon, the camera/UE must request UL resources before transmitting on the uplink. This likely involves additional signalling and latency which is detrimental to live production.
Further aspects of UL scheduling may be found in co-pending European patent application published under number EP3837895 [5], the contents of which are hereby incorporated by reference.
The lower layers (MAC and physical layers) of a mobile communication system are designed to create a radio waveform used for conveying data between a transmitter and receiver given some expected radio propagation conditions between the communicating gNB and the UE. In traditional link-layer designs, these layers are designed to allow the radio-communication system to cope with a given degree of radio propagation impairment. The success of mobile communication systems over the last few decades has been mainly due to the adoption of link adaptation that helps to maximise the throughput. In mobile communication systems such as 3G, 4G and 5G, the link-layer is designed with many choices for the forward error correction (FEC) code rates, modulation constellations, waveform type, transmit power levels. These can be jointly selected into sets of transmission parameters. Each set can be thought of as a parametrisation for the generation of the transmitted signal resulting from the joint choices that make the set. A given set is expected to generate a waveform or signal for transmission that is different from what another set would generate. Therefore, a deliberate choice can be made of a particular set of transmission parameters with the expectation that it would generate a transmission signal that is somehow more suitable for a prevailing set of radio channel propagation conditions than another set.
This method of designing link-layers is rather long-winded and laborious because it is difficult to deliberately determine the set of choices for all the configuration parameters. This is firstly, and especially, because the process of choosing between particular communication signal processing techniques such as FEC coding schemes (Low Density Parity Check (LDPC) codes, Turbo codes, or Polar codes, for example) is not trivial. Secondly, this is because even after a particular communication signal processing technique has been chosen, deciding on the set of possible configurations of the chosen technique that have to be designed and standardised is also an onerous process. As an example, if we consider only the FEC, then the radio communication system designer may have to first choose the FEC scheme (LDPC, Turbo or Polar codes etc.), then having chosen the FEC scheme, would need to then decide what block sizes and code rates to support etc. before proceeding to a similar process for modulation constellations etc.
Assuming that the radio-communication system has been designed already, such a system design has already chosen a coding scheme. In addition, it supports a designed number of possible codeword block sizes, a designed number of code rates per block size, a designed number of modulation constellations etc. Link adaptation allows the UE and gNB to work together to determine automatically:
This choice of an appropriate set of link-layer configuration parameters is also not trivial as it presents a somewhat multi-dimensional problem with the decision depending for example on the given transmission block size and the prevailing radio propagation channel conditions etc. Link adaptation in 4G and 5G systems is limited to the selection of a configuration from amongst a set of designed choices. For link adaptation of the downlink (DL), the UE measures channel quality parameters on the reception of reference signals transmitted by the BS. The channel quality is then signalled to the BS as a channel quality indicator (CQI) that can be either narrowband or wideband depending on the bandwidth of the reference signals used for its measurement. Based on this CQI report from the UE, the BS can adapt its DL transmissions to maximise throughput. Similarly, for the UL the BS measures channel quality parameters from reception of sounding reference signals (SRS) transmitted by the UE and uses the results of these measurements to instruct the UE how to adapt UL transmissions to maximise throughput. In 4G and 5G systems, since the FEC type for data channels is fixed, link adaptation therefore only involves the selection from a set of possible FEC code rates and modulation constellations—i.e. the modulation and coding scheme (MCS). Transmit power can also be thought of as an aspect of link adaptation, but is not typically adjusted per transmission block.
In cellular wireless communications, the channel between a mobile terminal and the base-station experiences typically rapid and significant variations which impacts the quality of the received signal. In the small-scale variation, the channel goes through frequency selective fading which results in rapid and random variations in the channel attenuation. In the large-scale variation, there are shadowing and distance related pathloss which affect the average received signal strength. In addition, there is interference arising from transmissions from nearby cells and terminals which distorts the signal at the receiver side.
In practice, the heart of mitigating and exploiting the variations of the channel condition is the scheduling mechanism that implements link adaptation algorithms, such as adaptive modulation and coding schemes (AMCS), dynamic power control and channel-dependent scheduling.
In NR, the downlink and uplink multi-user schedulers are located at the base-station (gNB) where, in principle, the scheduler assigns the resources for the users with the best channel conditions in a given instance in both the UL and DL while taking into account the fairness among users as well. There are two types of scheduling mechanism, and these are termed as dynamic scheduling (or dynamic grant) and semi-persistent scheduling (or configured grant).
In dynamic multi-user scheduling for downlink transmissions, based on the instantaneous channel condition where the terminal feeds back the channel quality indicator (CQI) derived from downlink reference signals (RS) at regular time-intervals to the gNB, the scheduler at the gNB, after receiving the CQI, decides the best modulation and coding scheme (MCS), best “available” frequency resources (physical resource blocks (PRBs)) and adequate power for the downlink data transmissions for some users at a given subframe/slot. The downlink scheduling decisions, which are known as scheduling assignments, are carried by downlink control information (DCI), which is transmitted in the downlink to the scheduled users.
Similarly, for the dynamic multi-user scheduling for uplink transmission, based on the instantaneous channel condition where the terminal sends channel SRS at regular time-intervals to the gNB, the scheduler at the gNB, after deriving the CQI based on the last received SRS, decides the best modulation and coding scheme, best frequency resources (PRBs) for the uplink data transmissions from some users at a given subframe/slot. The uplink scheduling decisions, which are also known as scheduling assignments, are carried by downlink control information (DCI) which is transmitted in the downlink to the scheduled users.
For semi-persistent scheduling (SPS) however, the resources are pre-configured semi-statically (e.g. via radio resource control (RRC) signalling) with a certain periodicity, where this periodicity is aligned with the data arrival rate for a particular service. There is an SPS for the downlink (known as DL SPS) and an SPS for the uplink (referred to as configured grant (CG)).
CG resources are mainly intended to deliver multiple traffic classes in a timely manner from the terminal, where such traffic classes have small data rates and some kind of periodicity, as specified in URLLC/IIoT in NR Rel-16/17. Some examples of the different traffic classes include industrial automation (future factory), energy power distribution, and intelligent transport systems, voice.
Issues with Legacy Scheduling Methods
As described above, CG resources are mainly intended for traffic with a low data rate and with some kind of periodicity, as specified in URLLC/IIoT in NR Rel-16/17. However, for traffic with a high data rate and which requires low latency, larger resources would be needed. In this case, a UE can be pre-configured with dedicated larger resources for such uplink data transmissions. These resources can be allocated by one of the following methods (or by a combination of these methods):
An issue with using pre-configured dedicated resources for uplink data transmissions is that the resources are always reserved in advance, regardless of whether a UE actually has data to transmit or not. Even though a UE is able to release these pre-configured resources after finishing its UL data transmissions, the concern is that the signalling and commands for re-allocating/re-activating the resources will come from the network, which may result in some unbearable delays for a variety of services like Heavy uplink URLLC, and will also involve signaling from the UE to request resources either via a scheduling request (SR), or initiating a RACH procedure, or will involve resources being configured for idle periods.
Another issue with pre-configured resources is that a UE may not be able to control completely the link adaptation parameters, such as frequency-domain scheduling, in order to choose the best frequency resources (PRBs) in a BWP, modulation and coding scheme (MCS), etc. Since the UE has to wait, after sending its measurements and/or SRS to the network, for the network to determine such link adaptation parameters and signal these to the UE, which both introduces latency and means that the most appropriate parameters may not be selected as the channel conditions may have changed between the time that the UE performed the measurements and/or transmitted the SRS and the time that the UE receives the link adaptation parameters from the gNB.
Another issue with pre-configured resources is that a UE may have to use all the resources whenever it has data to transmit, because the gNB and UE must be synchronised for the allocated resources. This may mean that a UE must add padding bits in order to fill the remaining resources. This is clearly not desirable, as it increases the UE's power consumption unnecessarily, and also generates interference for other UEs located in the same cell or in neighboring cells.
Accordingly, some enhancements for UL scheduling will be required for future mobile communications networks, such as 5G-Advanced and 6G. A set of requirements for such enhanced UL scheduling can be envisioned as listed below:
A solution to support UE-based scheduling in accordance with such requirements, where a UE is pre-assigned dedicated uplink resources for UL control and data transmissions in which these resources comprise UE-specific control resources and associated data resources, is provided in [5].
Here, the UE takes control of its own scheduling decisions (or assignments) for its UL data transmissions, which are to be confined within the pre-assigned dedicated resources. The UE-specific control resource 71 is always available for scheduling the UL data on a specific BWP. Hence, this solution addresses the requirements captured above, including ensuring immediate UL data transmission, provision of appropriate link adaptation and a flexible resource allocation scheme, providing an efficient way of identifying the UE, and improving the spectral efficiency of the cell. In
A communications device and an infrastructure equipment, such as the communications device 4 and infrastructure equipment 1 of
By configuring BWPs appropriately, the infrastructure equipment may provide BWPs which are suited for different types of services. For example, a BWP more suitable for eMBB may have a larger bandwidth in order to support high data rates. A BWP suited for URLLC services may use a higher sub-carrier spacing and shorter slot durations, in order to permit lower latency transmissions. Parameters of the wireless access interface which are applicable to a BWP may be referred to collectively as the numerology of a BWP. Examples of such parameters are sub-carrier spacing, symbol and slot durations and cyclic prefix length.
In the example in
A BWP may comprise communications resources for uplink or downlink communications. For a communications device, an uplink (UL) BWP and a downlink (DL) BWP may be independently configured, and an association (e.g. pairing) of an UL BWP and a DL BWP may be configured. In some examples, uplink and downlink communications resources are separated in time, in which case time division duplexing (TDD) may be used. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-id) may have the same centre frequency. In some examples uplink and downlink communications resources are separated in frequency, in which case frequency division duplexing (FDD) may be used. Where FDD is used, a UL BWP and a DL BWP may comprise two non-contiguous frequency ranges, one comprising communications resources for uplink communications and one comprising communications resources for downlink communications. In the remainder of the present disclosure, the term ‘bandwidth part’ (BWP) is used to refer to a pair of associated uplink and downlink bandwidth parts and as such, may comprise communications resources for both uplink and downlink transmissions. The terms ‘uplink bandwidth part’ and ‘downlink bandwidth part’ will be used where appropriate to refer to a bandwidth part comprising only, respectively, uplink communications resources and downlink communications resources.
An activated BWP refers to a BWP which may be used for the transmission or reception of data to or from the communications device 4, 14. An infrastructure equipment 1, 10 may schedule transmissions to or by the communications device 4, 14 only on a BWP if that BWP is currently activated for the communications device 4, 14. On deactivated BWPs, the communications device 4, 14 may not monitor a Physical Downlink Control Channel (PDCCH) and may not transmit on the Physical Uplink Control Channel (PUCCH), the Physical Random Access Channel (PRACH) and the Uplink Shared Channel (UL-SCH).
Conventionally, as illustrated in
A BWP may be designated as an initial downlink BWP, which provides the control resource set (CORESET) for downlink information used to schedule downlink transmissions of system information, and a corresponding initial uplink BWP for uplink transmissions for example for initiating PRACH transmission for initial access. When the communications device moves to connected mode, another BWP may be configured and activated as a first active BWP and then used for transmitting control information to or by the communications device 4, 14. The first active BWP can activate another configured BWP(s) if the first active BWP is unsuitable for an ongoing or new service or is insufficient e.g. due to congestion or lack of bandwidth. Alternatively or additionally, a BWP may be designated as a default BWP. If no BWP is explicitly configured as a default BWP, a BWP which is designated as the initial BWP may be the default BWP.
A default BWP may be defined as a BWP that a UE falls back to after an inactivity timer, associated with a BWP other than the default BWP, expires. For example, where a non-default BWP is deactivated as a result of an associated inactivity timer expiring, and no other non-default BWP is activated, then a default BWP may be activated in response. A default BWP may have an activation or deactivation priority which differs from the activation or deactivation priority of other, non-default, BWPs. A default BWP may be preferentially activated and/or may be deactivated with lowest preference. For example, a default BWP may remain activated unless and until a further BWP is to be activated such that a maximum number of activated BWPs would be exceeded. A default BWP may further be preferentially used for transmitting an indication that a different BWP is to be activated or de-activated.
Issues with BWP Switching for UE-Based Scheduling
For the UE-based scheduling mode, if UE currently operating on a wider BWP for transmitting a large data transmission, and then determines that it does not have any further data to transmit for some time, then the BWP inactivity timer (bwp-InactivityTimer) will expire and the UE will switch to a narrower BWP (like the default BWP or initial BWP) in order to reduce the power consumption as described above.
However, while the UE is operating on the narrower BWP, if the UE suddenly notices that some large data is available for transmission, where such data relates to delay-sensitive applications like XR services, the UE may need to activate and switch back to the wider BWP so that it can transmit this data immediately. In this regard, an assumption is being made that UE-based scheduling may only be configured on the wider BWPs (i.e., not on the narrower BWP), because the intention of UE-based scheduling is to transmit large data more efficiently.
In the legacy Rel-15/16/17 specifications, BWP activation and switching may be controlled by the reception of PDCCHs indicating a downlink assignment or an uplink grant for a specific BWP from the network. Alternatively, BWP activation and switching may be controlled by the bwp-InactivityTimer, by RRC signalling, or by the MAC entity upon initiation of a Random Access (RACH) procedure. For TDD (i.e., unpaired spectrum), a DL BWP is paired with an UL BWP with the same index, and BWP switching is common for both UL and DL (or at least, the switching happens at the same time).
It has been recognised by the present inventors that the existing BWP switching/activation methods, for example via PDCCH indication, is very slow. This is because the UE needs first to inform gNB, for example via a scheduling request (SR), that there is a large data available, and then the gNB needs to issue the activation/switching command via a further DCI indication for the UE to switch to the wider BWP. It is assumed that the BWP inactivity timer is not suitable here, as this is only used when there is no activity in the wider BWP, which then causes the UE to switch to narrower BWP, for power saving purposes. In addition, BWP switching controlled by the MAC entity is only used when the UE initiates a RACH procedure.
Accordingly, this embodiments of the present disclosure seek to address and provide solutions to the issue of switching to a wider BWP immediately when the UE is currently operating on a narrower BWP, where the UE is configured with the UE-based scheduling mode and determines that it has a large portion of data to transmit.
As shown in the example of
Essentially, embodiments of the present technique propose that a UE is able to autonomously activate and switch to a wider BWP in order to employ UE-based scheduling mode techniques—i.e. where the UE schedules itself on the resources of the wider BWP. In this case, the UE transmits scheduling control information (e.g., carried by PUCCH) and the associated data (e.g., carried by PUSCH) on the wider BWP. The gNB monitors the control resources in every occasion, and checks whether the UE has transmitted the control information (e.g., PUCCH) and, accordingly, the associated data on the wider BWP.
At time t0 to time t1, the UE is in the wider BWP 101 (for both DL and UL) as it has a large portion of data to transmit, and as such applies the UE-based scheduling mode in the uplink. In this period the UE behaves as shown in, for example,
Suddenly, the UE notices that a large portion of data is available for transmission, where this data relates to a delay sensitive application such as to XR services, and so the UE needs to switch to the wider BWP1 101 again in order to transmit this data. In this case, between time t2 and time t3, the UE activates and switches to the wider BWP 101 autonomously and then schedules itself on the resources on the wider BWP 101 by employing the UE-based scheduling procedure. As the gNB has been constantly monitoring the control resources of the wider BWP 101, it will detect the control information (e.g., PUCCH) which indicates the scheduling information of the UE, and then will be able to successfully receive the associated data (which is carried, for example, by a PUSCH). The UE may then continue to schedule itself as long as it has data to transmit in the subsequent time slots.
Further, at time t3 (until, for example, time t4), the UE does not have any data to transmit and so the inactivity timer (e.g. bwp-InactivityTimer) again expires. Accordingly, the UE falls back to the narrower BWP2 102 in order to reduce power consumption. Here, as shown in the example of
It should be noted here that—in accordance with embodiments of the present disclosure—when a UE activates a BWP and switches from a current BWP to that newly activated BWP, it also deactivates the current BWP. This is the legacy behaviour from Rel-15 onward. Further detail with respect to the actions of BWP activation and deactivation may be found in, for example, [6]. In other words, in accordance with embodiments of the present disclosure, as the skilled person would appreciate, when switching between two BWPs, the communications device may be configured to deactivate the BWP being switched from and to activate the BWP being switched to.
Furthermore, it should be noted that UEs which are able to autonomously switch to a wider BWP and schedule and transmit uplink data in accordance with the UE-based scheduling mode may be a certain class(es) of UEs, or UEs which are configured to transmit data in accordance with certain applications or services (for example XR or heavy uplink URLLC). Such UEs (or any other subset of UEs) may be configured by the network to allow them to operate in accordance with such autonomous switching and UE-based scheduling behaviour, or to stop operating in such a manner.
The only drawback of the method illustrated by
In some arrangements of embodiments of the present technique, after a UE activates and switches to the narrower BWP, the UE does not apply the UE-based scheduling mode. The motivation is that the UE can only transmit small portions of data, for example configured grant (CG) data, where the CG resources may be configured to be periodic based on the traffic profile of the CG data. In other words, the communications device may be configured, while operating on the first BWP, to determine that the communications device has second uplink data to transmit to the wireless communications network (where the second uplink data may be smaller than the predetermined size), and to transmit, to the wireless communications network, the second uplink data within configured grant, CG, resources of the first BWP. Here, the CG resources may be one instance of a sequence of periodically occurring instances of uplink communications resources of the first BWP. In response to transmitting the small CG (i.e. second) data, the communications device may be configured to receive, from the wireless communications network, an indication that the communications device is to switch from the first BWP to the second BWP and is to transmit any further uplink data within the second BWP in accordance with the communications device based scheduling mode.
In some arrangements of embodiments of the present technique, after a UE activates and switches to the narrower BWP, the UE may inform the network about the availability of any subsequent large data in its buffer via, for example, a scheduling request (SR), since the UE is not at this time applying the UE-based scheduling mode. Upon receiving the SR, the network is able to configure the UE to activate and switch to the wider BWP, and instruct the UE to transmit UL data in accordance with the UE-based scheduling procedure in the subsequent time slots. In other words, the communications device may be configured, after switching from the second BWP to the first BWP, to determine that the communications device has second uplink data to transmit to the wireless communications network (where the second uplink data may be equal to or greater than the predetermined size), to transmit, to the wireless communications network in response to determining that the communications device has the second uplink data to transmit to the wireless communications network, a scheduling request, and to receive, from the wireless communications network in response to the transmitted scheduling request, an indication that the communications device is to switch from the first BWP to the second BWP and is to transmit the second uplink data within the second BWP in accordance with the communications device based scheduling mode.
In some arrangements of embodiments of the present technique, after a UE activates and switches to the narrower BWP, the UE starts a new timer. If this timer expires, the UE switches to the larger BWP. In other words, the communications device may be configured to determine that a second specified period has elapsed after switching from the second BWP to the first BWP, and to switch, in response to determining that the second specified period has elapsed, from the first BWP to the second BWP. This new timer may be aligned with the arrival of data (i.e. a new large amount of UL data) on the wider BWP. In other words, the second specified period is a period between the communications device switching from the second BWP to the first BWP and the communications device having second uplink data to transmit to the wireless communications network (where the second uplink data may be equal to or greater than the predetermined size). Here, both of the uplink data and the second uplink data may be instances of periodic uplink data, where one or more of these instances of periodic uplink data may be equal to or greater than the predetermined size.
In some arrangements of embodiments of the present technique, a UE (which, like UEs/communications devices described herein in accordance with embodiments of the present technique generally, has been configured in advance by the network to be able to operate in accordance with the UE-based scheduling mode) may change its strategy of uplink BWP activation/switching depending on power class of the UE, and or transmission power headroom (PHR) available to the UE, and/or on a UE's position within the cell (which may be detected, for example, based on a level of pathloss between the UE and gNB). In other words, the communications device may be configured to determine whether the communications device is to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data is based on one or more of: a power class of the communications device, a capability of the communications device, a power headroom of the communications device, and a level of pathloss between the communications device and the wireless communications network.
The downlink power is shared among different users, and the gNB is able to re-allocate the power to other UEs. When a downlink bandwidth part is expanded, the gNB can allocate more power for it. On the other hand, uplink power cannot exceed the UE's own maximum power (max power capability is defined by the UE's Power class). So, when the UE is located at the cell edge, the room of remaining Tx power (i.e. power headroom (PHR)) is limited. A UE cannot generally easily expand the uplink bandwidth part (i.e. switch from a narrower BWP to a wider BWP) at the cell edge, unless the UE is a high power class UE. The UE's power class is defined in that UE's capability. For example, in frequency range 2 (FR2) (i.e. mmWave), power class 1 is 35 dBm for high throughput UEs like fixed wireless access UEs, while others are 23 dBm. In frequency range 1 (FR1) (i.e. 410 MHz to 7125 MHz), power class 2 is a maximum of 26 dBm, and power class 3 is 23 dBm. Further power classes may be newly defined and added in the future for different types of UEs/applications. By contrast, a UE that is located more closely to the cell center can dynamically expand the bandwidth part (i.e. switch from a narrower BWP to a wider BWP) because the UE has still more power headroom.
In the former case, where the UE is unable to switch to a wider BWP, the UE may indicate such a status to the gNB, where this indication may be conveyed via uplink control information (UCI). In other words, the communications device may be configured to determine that the communications device is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data. Here, the communications device may be configured to transmit, to the wireless communications network, an indication that the communications device is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data. Then, the gNB will be aware that the UE cannot change the uplink bandwidth part (e.g. based on limited PHR available to that UE). Based on the indication, gNB may change the UL scheduling strategy to a time domain solution rather than a frequency domain solution (i.e. switching bandwidth part). For example, the strategy may be changed to one which employs repetition of time resources, or instructing the UE to fall back to gNB-based scheduling. An example of such a scheduling strategy is that the gNB may use a low order modulation scheme (e.g. QPSK) rather than a higher order modulation scheme (e.g. 64 QAM), and/or may select a lower coding rate (i.e. utilising more parity bits for error correction). This may mitigate losses in peak transmission power, though instead has a downside of requiring more time resources for transmitting the same amount of data. In other words, the communications device may be configured to receive, from the wireless communications network, an indication that the communications device is to operate in accordance with a second communications device based scheduling mode in order to transmit the uplink data, and the method comprises, as the second communications device based scheduling mode, to transmit, to the wireless communications network within a control resource of the first BWP, scheduling information indicating that the communications device is to transmit the uplink data to the wireless communications network, and to transmit, to the wireless communications network within a data resource of the first BWP, the uplink data in accordance with the transmitted scheduling information, wherein the data resource of the first BWP has a smaller bandwidth than the data resource of the second BWP, and wherein the transmitting the uplink data within the data resource of the first BWP comprises transmitting the uplink data over a longer time period than if the uplink data was transmitted within the data resource of the second BWP. Alternatively (or in addition), the communications device may be configured to receive, from the wireless communications network, an uplink grant indicating resources within the first BWP in which the communications device is to transmit the uplink data, and to transmit, to the wireless communications network, the uplink data in the resources within the first BWP indicated by the uplink grant.
Alternatively, instead of receiving such an indication (e.g. via UCI), the gNB may use other information indirectly (i.e. by detecting or knowing such information itself) such as the UE's transmission power headroom (PHR), the level of pathloss between the UE and the gNB, the UE's power class, etc., in order to change the UL scheduling strategy. In other words, the infrastructure equipment may be configured to determine that the communications device will independently determine that it is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data, wherein the determining that the communications device will independently determine that it is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data is based on one or more of: a power class of the communications device, a capability of the communications device, a power headroom of the communications device, and a level of pathloss between the communications device and the wireless communications network.
The method begins in step S1. The method comprises, in step S2, determining that the communications device has uplink data to transmit to the wireless communications network. In step S3, the process comprises determining, whether the communications device is to operate in accordance with a communications device based scheduling mode in order to transmit the uplink data. Then, in step S4, if the communications device determines in step S3 that it is to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data, the process comprises, as a first step of the communications device based scheduling mode, switching from a first bandwidth part, BWP, of the wireless radio interface to a second BWP of the wireless radio interface for transmission of the uplink data, wherein the second BWP has a greater bandwidth than the first BWP and comprises a control resource and a data resource. In step S5, the method comprises, as a second step of the communications device based scheduling mode, transmitting, to the wireless communications network within the control resource, scheduling information indicating that the communications device is to transmit at least part of the uplink data to the wireless communications network. Then, in step S6, the process comprises, as a third step of the communications device based scheduling mode, transmitting, to the wireless communications network within the data resource, the at least part of the uplink data in accordance with the transmitted scheduling information. The process ends in step S7.
However, if in step S4 the communications device determines that it is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data, the process (in accordance with the example process of communications in a communications system in accordance with embodiments of the present technique illustrated by
Those skilled in the art would appreciate that the method shown by
Those skilled in the art would further appreciate that such infrastructure equipment and/or communications devices as herein defined may be further defined in accordance with the various arrangements and embodiments discussed in the preceding paragraphs. It would be further appreciated by those skilled in the art that such infrastructure equipment and communications devices as herein defined and described may form part of communications systems other than those defined by the present disclosure.
The following numbered paragraphs provide further example aspects and features of the present technique:
Paragraph 1. A method of operating a communications device configured to transmit signals to and/or to receive signals from a wireless communications network via a wireless radio interface provided by the wireless communications network, the method comprising
Paragraph 2. A method according to Paragraph 1, wherein the location of the control resource within the second BWP is preconfigured and known to both the communications device and the wireless communications network.
Paragraph 3. A method according to Paragraph 1 or Paragraph 2, comprising
Paragraph 4. A method according to Paragraph 3, comprising, after switching from the second BWP to the first BWP,
Paragraph 5. A method according to Paragraph 3 or Paragraph 4, comprising
Paragraph 6. A method according to Paragraph 5, wherein the second specified period is a period between the communications device switching from the second BWP to the first BWP and the communications device having second uplink data to transmit to the wireless communications network.
Paragraph 7. A method according to Paragraph 6, wherein both of the uplink data and the second uplink data are instances of periodic uplink data.
Paragraph 8. A method according to any of Paragraphs 3 to 7, wherein the switching from the first BWP to the second BWP and the switching from the second BWP to the first BWP are performed periodically by the communications device.
Paragraph 9. A method according to any of Paragraphs 1 to 8, comprising, while operating on the first BWP,
Paragraph 10. A method according to Paragraph 9, wherein the CG resources are one instance of a sequence of periodically occurring instances of uplink communications resources of the first BWP.
Paragraph 11. A method according to Paragraph 9 or Paragraph 10, comprising
Paragraph 12. A method according to any of Paragraphs 1 to 11, wherein the determining whether the communications device is to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data is based on one or more of:
Paragraph 13. A method according to Paragraph 12, comprising
Paragraph 14. A method according to Paragraph 13, comprising
Paragraph 15. A method according to Paragraph 13 or Paragraph 14, comprising
Paragraph 16. A method according to any of Paragraphs 13 to 15, comprising
Paragraph 17. A method according to any of Paragraphs 1 to 16, comprising, when switching between two BWPs,
Paragraph 18. A method according to any of Paragraphs 1 to 17, wherein the first BWP is a default BWP.
Paragraph 19. A method according to any of Paragraphs 1 to 18, wherein the first BWP is an initial BWP.
Paragraph 20. A method according to any of Paragraphs 1 to 19, wherein the scheduling information is transmitted within a Physical Uplink Control Channel, PUCCH.
Paragraph 21. A method according to any of Paragraphs 1 to 20, wherein the uplink data is transmitted within a Physical Uplink Shared Channel, PUSCH.
Paragraph 22. A method according to any of Paragraphs 1 to 21, wherein the uplink data is equal to or greater than a predetermined size.
Paragraph 23. A method according to any of Paragraphs 1 to 22, wherein the uplink data that the communications device determines it has to transmit to the wireless communications network is the total amount of uplink data available for transmission in a buffer of the communications device.
Paragraph 24. A communications device comprising
Paragraph 25. Circuitry for a communications device comprising
Paragraph 26. A method of operating an infrastructure equipment forming part of a wireless communications network, the infrastructure equipment being configured to transmit signals to and/or to receive signals from a communications device via a wireless radio interface provided by the infrastructure equipment, the method comprising
Paragraph 27. A method according to Paragraph 26, wherein the location of the control resource within the second BWP is preconfigured and known to both the communications device and infrastructure equipment.
Paragraph 28. A method according to Paragraph 26 or Paragraph 27, comprising
Paragraph 29. A method according to Paragraph 28, comprising, after the communications device has switched from the second BWP to the first BWP,
Paragraph 30. A method according to Paragraph 28 or Paragraph 29, comprising
Paragraph 31. A method according to Paragraph 30, wherein the second specified period is a period between the communications device switching from the second BWP to the first BWP and the communications device having second uplink data to transmit to the wireless communications network.
Paragraph 32. A method according to Paragraph 31, wherein both of the uplink data and the second uplink data are instances of periodic uplink data.
Paragraph 33. A method according to any of Paragraphs 28 to 32, comprising
Paragraph 34. A method according to any of Paragraphs 26 to 33, comprising
Paragraph 35. A method according to Paragraph 34, wherein the CG resources are one instance of a sequence of periodically occurring instances of uplink communications resources of the first BWP.
Paragraph 36. A method according to Paragraph 34 or Paragraph 35, comprising
Paragraph 37. A method according to any of Paragraphs 26 to 36, comprising
Paragraph 38. A method according to Paragraph 37, comprising
Paragraph 39. A method according to Paragraph 37 or Paragraph 38, wherein the determining that the communications device will independently determine that it is not to operate in accordance with the communications device based scheduling mode in order to transmit the uplink data is based on one or more of:
Paragraph 40. A method according to any of Paragraphs 37 to 39, comprising
Paragraph 41. A method according to any of Paragraphs 37 to 40, comprising
Paragraph 42. A method according to any of Paragraphs 26 to 41, wherein the first BWP is a default BWP.
Paragraph 43. A method according to any of Paragraphs 26 to 42, wherein the first BWP is an initial BWP.
Paragraph 44. A method according to any of Paragraphs 26 to 43, wherein the scheduling information is received within a Physical Uplink Control Channel, PUCCH.
Paragraph 45. A method according to any of Paragraphs 26 to 44, wherein the uplink data is received within a Physical Uplink Shared Channel, PUSCH.
Paragraph 46. A method according to any of Paragraphs 26 to 45, wherein the uplink data is equal to or greater than a predetermined size.
Paragraph 47. A method according to any of Paragraphs 26 to 46, wherein the uplink data that the infrastructure equipment determines the communications device has to transmit to the infrastructure equipment is the total amount of uplink data available for transmission in a buffer of the communications device.
Paragraph 48. An infrastructure equipment forming part of a wireless communications network, the infrastructure equipment comprising
Paragraph 49. Circuitry for an infrastructure equipment forming part of a wireless communications network, the infrastructure equipment comprising
Paragraph 50. A wireless communications system comprising a communications device according to Paragraph 24 and an infrastructure equipment according to Paragraph 48.
Paragraph 51. A computer program comprising instructions which, when loaded onto a computer, cause the computer to perform a method according to any of Paragraphs 1 to 23 or Paragraphs 26 to 47. Paragraph 52. A non-transitory computer-readable storage medium storing a computer program according to Paragraph 51.
It will be appreciated that the above description for clarity has described embodiments with reference to different functional units, circuitry and/or processors. However, it will be apparent that any suitable distribution of functionality between different functional units, circuitry and/or processors may be used without detracting from the embodiments.
Described embodiments may be implemented in any suitable form including hardware, software, firmware or any combination of these. Described embodiments may optionally be implemented at least partly as computer software running on one or more data processors and/or digital signal processors. The elements and components of any embodiment may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units. As such, the disclosed embodiments may be implemented in a single unit or may be physically and functionally distributed between different units, circuitry and/or processors.
Although the present disclosure has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognise that various features of the described embodiments may be combined in any manner suitable to implement the technique.
Number | Date | Country | Kind |
---|---|---|---|
22153309.4 | Jan 2022 | EP | regional |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2022/087258 | 12/21/2022 | WO |