D E S C R I P T I O N

MULTIPLE UPLINK BANDWIDTH PARTS OF INITIAL ACCESS OF REDUCED-CAPABILITY DEVICES

TECHNICAL FIELD

Various examples of the disclosure generally relate to operating multiple bandwidth parts for wireless communication devices of different types identified at a cellular network as supporting different bandwidths.

BACKGROUND

In the Third Generation Partnership Project (3GPP) Release 15, the so-called 5G system has been first specified for cellular networks (NWs). 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). Wireless communication devices (UEs) operating according to NR can be referred to as reference UEs (or, baseline UEs).

3GPP Release 17 specifies the so-called NR-light features as extension of 5G. Here, lower-capability wireless communication devices called RedCap UEs are specified (from Reduced Capability).

One of the reduced system requirements pertains to the hardware-supported bandwidth (BW). RedCap UEs are identified/listed at the cellular NW as having a limited hardware-supported bandwidth. For instance, RedCap UEs may be listed at the cellular NW to support a maximum BW of 100 MHz for FR2 carrier frequencies (e.g., 24250 - 52600 MHz) and of 20 MHz for FR1 carrier frequencies (e.g., 450 - 6000 MHz). These frequency ranges are defined, e.g., in 3GPP Technical Specification (TS) 38.101 -1 V17.0.0 (2020-12). The respective hardware-supported BW can be re- duced accordingly, thereby allowing lower complexity devices. Examples are described in 3GPP document RP-202933 (“New WID on support of reduced capability NR devices”).

RedCap UEs can, e.g., be smart watches, wearable medical devices, augmented-re- ality goggles, industrial wireless sensors, surveillance cameras, etc.

To support the reduced hardware-supported bandwidth of RedCap UEs, it is possible to operate respective bandwidth parts (BWPs) that have sufficiently small BWs to support the limited hardware-supported BW of RedCap UEs. A BWP is a contiguous set of physical resource blocks, i.e., sets of time-frequency resources, on a carrier. Different BWPs can have different numerologies, i.e., different subcarrier spacing, symbol duration, and cyclic prefix length. Different BWPs can have different BWs. Therefore, RedCap UEs can be configured to operate in/use BWPs that have sufficiently small BWs to support the limited hardware-supported BW of RedCap UEs.

However, it has been observed that coexistence of small-BW (e.g., for RedCap UEs) and large-BW BWPs (e.g., for reference UEs) can cause interoperability problems. For instance, presence of an uplink (UL) small-BW BWP for RedCap UEs arranged at overlapping frequencies with a large-BW BWP for reference UEs is known to potentially cause resource fragmentation of the large-BW BWP for reference UEs, i.e., splitting the otherwise contiguous set of physical resource blocks for reference UEs; this complicates scheduling and can cause interference and reduce UL peak data rate for reference UEs requiring contiguous frequency resource allocation. See 3GPP R1 -2108498 (“FL summary #6 on reduced maximum UE bandwidth for RedCap”), section 3.3. Also see 3GPP R1 -2106563 (“Reduced maximum UE bandwidth for RedCap”).

SUMMARY

Accordingly, a need exists for advanced techniques of operating BWPs for UEs of different categories having different maximum hardware-supported BWs.

This need is met by the features of the independent claims. The features of the dependent claims define embodiments. A method of operating an access node of a cellular network is provided. The method includes operating, for first wireless communication devices of a first device type, a first uplink bandwidth part having a first bandwidth. The method also includes, while operating the first uplink bandwidth part, operating, for initial access of second wireless communication devices of a second device type, multiple second initial uplink bandwidth parts having one or more second bandwidths that are smaller than the first bandwidth. The second device type is identified at the cellular network is not supporting the entire first bandwidth (i.e., as not supporting an entirety of the first bandwidth).

The second device type may be identified at the cellular network as supporting a further bandwidth that is smaller than the first bandwidth.

The second device type may be reduced capability devices.

Operating a bandwidth part may generally pertain to determining a respective configuration and transmitting and/or receiving data on the bandwidth part in accordance with the configuration.

The first wireless communication devices of the first device type, accordingly, may be required to use the first uplink bandwidth part, but not the one or more second initial uplink bandwidth parts. The second wireless communication devices of the second device type, accordingly, may be required to use at least one of the one or more second bandwidth parts, but not the first bandwidth part.

A computer program or a computer-program product or a computer-readable storage medium includes program code. The program code can be loaded and executed by at least one processor. The at least one processor, upon executing the program code, performs a method of operating an access node of a cellular network is provided. The method includes operating, for first wireless communication devices of a first device type, a first uplink bandwidth part having a first bandwidth. The method also includes, while operating the first uplink bandwidth part, operating, for initial access of second wireless communication devices of a second device type, multiple second initial uplink bandwidth parts having one or more second bandwidths that are smaller than the first bandwidth. The second device type is identified at the cellular network is not supporting the entire first bandwidth. An access node of a cellular network includes a processor. The processor is configured to operate for first wireless communication devices of a first device type, a first uplink bandwidth part having a first bandwidth. The processor is further configured, while operating the first uplink bandwidth part, to operate, for initial access of second wireless communication devices of a second device type, multiple second initial uplink bandwidth parts having one or more second bandwidths that are smaller than the first bandwidth. The second device type is identified at the cellular network is not supporting the entire first bandwidth (i.e. , as not supporting an entirety of the first bandwidth).

A method of operating a wireless communication device of a device type classified at a cellular network as not supporting an entire first bandwidth of a first uplink bandwidth part operated by a cellular network includes obtaining a configuration of multiple second initial uplink bandwidth parts. The multiple second initial uplink bandwidth parts are assigned to the device type and have one more second bandwidths that are smaller than the first bandwidth. The method also includes transmitting uplink data of an initial access procedure to the cellular network in at least one of the multiple second initial uplink bandwidth parts and in accordance with the configuration.

The multiple second initial uplink bandwidth parts may or may not have different second bandwidths.

A computer program or a computer-program product or a computer-readable storage medium includes program code. The program code can be loaded and executed by at least one processor. The at least one processor, upon executing the program code, performs a method of operating a wireless communication device of a device type classified at a cellular network as not supporting an entire first bandwidth of a first uplink bandwidth part operated by a cellular network. The method Includes obtaining a configuration of multiple second initial uplink bandwidth parts. The multiple second initial uplink bandwidth parts are assigned to the device type and have one more second bandwidths that are smaller than the first bandwidth. The method also includes transmitting uplink data of an initial access procedure to the cellular network in at least one of the multiple 2nd initial uplink bandwidth parts and in accordance with the configuration. A wireless communication device of a device type classified at the cellular network as not supporting an entire first bandwidth of a first uplink bandwidth part that is operated by the cellular network includes a processor. The processor is configured to obtain a configuration of multiple second initial uplink bandwidth parts that are assigned to the device and have one more second bandwidths that are smaller than the first bandwidth. The processor is further configured to transmit uplink data of an initial access procedure to the cellular network in at least one of the multiple second initial uplink bandwidth parts and in accordance with the configuration.

It is to be understood that the features mentioned above and those yet to be explained below may be used not only in the respective combinations indicated, but also in other combinations or in isolation without departing from the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a cellular network according to various examples.

FIG. 2 schematically illustrates resources of a time-frequency resource grid allocated to different channels according to various examples.

FIG. 3 schematically illustrates bandwidth parts according to various examples.

FIG. 4 schematically illustrates multiple modes in which a UE can operate, as well as transitions between the multiple modes according to various examples.

FIG. 5 schematically illustrates a protocol for finding an initial UL bandwidth part in an initial downlink bandwidth part according to various examples.

FIG. 6 is a signaling diagram of communication between a UE and a base station according to various examples.

FIG. 7 schematically illustrates reference implementations of initial UL bandwidth parts for reduced capability UEs.

FIG. 8 schematically illustrates initial UL bandwidth parts operated in parallel for reduced capability UEs according to various examples. FIG. 9 schematically illustrates a base station according to various examples.

FIG. 10 schematically illustrates a UE according to various examples.

FIG. 11 is a flowchart of a method according to various examples.

FIG. 12 is a flowchart of a method according to various examples.

DETAILED DESCRIPTION

Some examples of the present disclosure generally provide for a plurality of circuits or other electrical devices. All references to the circuits and other electrical devices and the functionality provided by each are not intended to be limited to encompassing only what is illustrated and described herein. While particular labels may be assigned to the various circuits or other electrical devices disclosed, such labels are not intended to limit the scope of operation for the circuits and the other electrical devices. Such circuits and other electrical devices may be combined with each other and/or separated in any manner based on the particular type of electrical implementation that is desired. It is recognized that any circuit or other electrical device disclosed herein may include any number of microcontrollers, a graphics processor unit (GPU), integrated circuits, memory devices (e.g., FLASH, random access memory (RAM), read only memory (ROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), or other suitable variants thereof), and software which co-act with one another to perform operation(s) disclosed herein. In addition, any one or more of the electrical devices may be configured to execute a program code that is embodied in a non-transi- tory computer readable medium programmed to perform any number of the functions as disclosed.

In the following, embodiments of the invention will be described in detail with reference to the accompanying drawings. It is to be understood that the following description of embodiments is not to be taken in a limiting sense. The scope of the invention is not intended to be limited by the embodiments described hereinafter or by the drawings, which are taken to be illustrative only. The drawings are to be regarded as being schematic representations and elements illustrated in the drawings are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose become apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof.

Various examples of the disclosure are generally related to communication between UEs and a communications NW such as a cellular NW. Hereinafter, reference is made to a cellular NW, but similar techniques may be applicable to other types of communication NWs.

According to the techniques described herein, UEs having different capabilities can be operated in the same cellular NW and served by the same access node. UEs of different categories can be operated. For instance,, UEs of a first type can be identified at the cellular NW to have first capabilities; while UEs of a second type can be identified at the cellular to have different second capabilities (while herein the term “type” of UE is used, it would also be possible to use “category” of UEs). The hardware capabilities of UEs of the first and second categories may differ in accordance with such identification I listing at the cellular NW.

Coexistence between such UEs of categories associated with different capabilities can be facilitated according to the techniques disclosed herein, i.e. , it can be ensured that UEs of both categories can be served by a given access node - i.e., a base station (BS) of a cellular NW.

According to various examples of the disclosure, UEs can be of the following categories, summarized in TAB. 1.

TAB. 1 : Different UE categories. These UE categories can be identified for the respective UEs at the cellular NW. For instance, the device type may be listed in a UE context at a mobility control node of the cellular NW. The respective UEs may implicitly or explicitly signal their type to the cellular NW, e.g., by selecting appropriate resources, transmitting an identifier that is indicative of the type, selecting an appropriate random-access (RA) preamble, etc..

To facilitate operation of RedCap UE, it is possible to use BWPs that are specifically assigned to such RedCap-UE (RedCap-BWPs). Specifically, such RedCap-BWPs can have a BW that is narrower than or equal to a maximum BW associated with the RedCap UE type. Reference UEs shall not use the configuration of RedCap-BWPs. A RedCap-UE can then use, at any given point in time, a single one of the RedCap- BWPs - thereby being able to communicate with the cellular NW even in view of its limited maximum BW.

According to techniques disclosed herein, different strategies for operating RedCap- BWPs as well as BWPs assigned to the reference UEs (reference-BWPs) are provided. Specifically, techniques are disclosed for operating multiple UL RedCap-BWPs overlapping frequency domain with a reference BWP. A RedCap UE may be generally eligible to access any one of the multiple UL RedCap-BWPs. The multiple UL RedCap-BWPs may all be associated with the same DL RedCap-BWP. However, since - at a given moment of time - there is only one active BWP for each UE, each UE may determine which specific one of the multiple UL RedCap-BWPs to access at a given moment of time. A usage rule may be employed that may be predefined or communicated between the RedCap-UE and the cellular NW (shared between the RedCap-UE and the cellular NW). It would be possible to use frequency hopping to subsequently transmit on different ones of the multiple UL RedCap-BWPs. Because of the BW-limited radio-frequency hardware of the RedCap-UE, a time offset - e.g., in the order of a millisecond or less, e.g., a few tens of microseconds - for re-tuning of radio-frequency oscillator may be implemented; here the RedCap-UE cannot transmit (or receive) data.

Specifically, multiple initial UL RedCap-BWPs may be operated. A RedCap-UE may thus transmit data - e.g., control signals on a control channel and/or control messages on a shared channel - of an initial-access procedure on the at least one initial UL RedCap-BWP that is determined based on the multiple initial UL RedCap-BWPs serving as candidates.

As used herein, “operating a BWP” can pertain to determining a respective configuration and providing the configuration to one or more UEs, e.g., using a broadcast message or using dedicated control signaling. Alternatively or additionally, “operating a BWP” can furthermore include transmitting and/or receiving using a numerology associated with that BWP, i.e. , using the BWP to transmit or receive data. Alternatively or additionally, “operating a BWP” can furthermore pertain to defining one or more channels, e.g., control and/or shared channels on the respective BWP. Alternatively or additionally, “operating a BWP” can mean that the respective BWP is available for communication with UEs of a given type. Alternatively or additionally, “operating a BWP” can mean that the respective BWP is carried out a specific function, such as initial BWP is a BWP to support initial access procedure/function.

By using multiple initial UL RedCap-BWPs, additional capacity can be provided. More RedCap UEs can be served.

FIG. 1 schematically illustrates a cellular network 100. The example of FIG. 1 illustrates the network 100 according to the 3GPP 5G architecture. Details of the 3GPP 5G architecture are described in 3GPP TS 23.501 , version 17.0.0 (2021 -03-30). The 3GPP 5G architecture can support RedCap UEs and reference UEs (cf. TAB. 1 ). In the scenario of FIG. 1 , a UE 101 is connectable to the cellular network 100. For example, the UE 101 may be one of the following: a cellular phone; a smart phone; and loT device; a MTC device; a sensor; an actuator; etc. Specifically, the UE 101 can be a RedCap UE 101 (cf. TAB. 1 ).

Also illustrated is a reference UE 91 (cf. TAB. 1 ).

The UEs 91 , 101 are connectable to the network 100 via a RAN 111 , typically formed by one or more BSs 112 (only a single BS 112 is illustrated in FIG. 1 for sake of simplicity; the BSs implement ANs). A wireless link 114 is established between the RAN 111 - specifically between one or more of the BSs 112 of the RAN 111 - and the UEs 91 , 101. The wireless link 114 is defined by one or more Orthogonal Frequency Division Multiple (OFDM) carriers.

The RAN 111 is connected to a core network (CN) 115. The CN 115 includes a user plane (UP) 191 and a control plane (CP) 192. Application data is typically routed via the UP 191. For this, there is provided a UP function (UPF) 121. The UPF 121 may implement router functionality. Application data may pass through one or more UPFs 121 . In the scenario of FIG. 1 , the UPF 121 acts as a gateway towards a data network 180, e.g., the Internet or a Local Area Network. Application data can be communicated between each one of the UEs 91 , 101 and one or more servers on the data network 180.

The network 100 also includes an Access and Mobility Management Function (AMF) 131 ; a Session Management Function (SMF) 132; a Policy Control Function (PCF) 133; an Application Function (AF) 134; a Network Slice Selection Function (NSSF) 134; an Authentication Server Function (AUSF) 136; a Unified Data Management (UDM) 137; and a Location Management Function (LMF) 139. FIG. 1 also illustrates the protocol reference points N1 -N22 between these nodes.

The AMF 131 provides one or more of the following functionalities: registration management; NAS termination; connection management; reachability management; mobility management; access authentication; and access authorization. A data connection 189 is established by the AMF 131 if the respective UE 91 , 101 operates in a connected mode. For instance, the AMF 131 may identify the RedCap UE 101 as having the RedCap device type; and may identify the reference UE 91 as having a legacy/reference device type.

The AMF 131 may thus identify the UE 101 as not supporting the entire BW of a carrier of the wireless link 114 or, at least, a reference-BWP assigned to the reference device type.

Such identification of each one of the UEs 91 , 101 as belonging to a given device type may be stored in respective UE contexts 459.

The SMF 132 provides one or more of the following functionalities: session management including session establishment, modify and release, including bearers set up of UP bearers between the RAN 111 and the UPF 121 ; selection and control of UPFs; configuring of traffic steering; roaming functionality; termination of at least parts of NAS messages; etc. As such, the AMF 131 and the SMF 132 both implement CP mobility management needed to support a moving UE.

A respective data connection 189 is established between each one of the UEs 91 , 101 via the RAN 111 and the data plane 191 of the CN 115 and towards the DN 180. For example, a connection with the Internet or another packet data network can be established. To establish the data connection 189, it is possible that the respective UE 91 , 101 performs an initial access procedure, specifically a random access (RACH) procedure, e.g., initial access from RRCJDLE mode to RRC_CONNECTED mode, in response to reception of a paging indicator or paging message. A server of the DN 180 may host a service for which payload data is communicated via the data connection 189. The data connection 189 may include one or more bearers such as a dedicated bearer or a default bearer. The data connection 189 may be defined on the Radio Resource Control (RRC) layer, e.g., generally Layer 3 of the OSI model of Layer 2.

FIG. 2 illustrates aspects with respect to channels 261 -263 implemented on the wireless link 114. The wireless link 114 implements a plurality of channels 261-263. The resources of the channels 261-263 are offset from each other, e.g., in frequency do- main and/or time domain, in accordance with a respective resource mapping. The resources may be defined in a time-frequency grid defined by the symbols and subcarriers of the OFDM modulation of the carrier.

A first channel 261 may be an UL shared channel - e.g., Physical UL Shared Channel (PLISCH) according to the 3GPP NR specification. Here, symbols encoding messages including payload data, e.g., Layer 3 or higher, may be communicated. Payload data may be associated with an application supported by a data connection 189 or may pertain to Layer 3 control signaling (Radio Resource Control, RRC, messages, e.g., for providing a configuration of a BWP).

A second channel 262 may be an UL control channel, e.g., Physical UL Control Channel (PUCCH) according to the 3GPP NR specification. Here, positive or negative acknowledgements of messages communicated on a downlink shared channel 263 - e.g., Physical Downlink Shared Channel (PDSCH) according to the 3GPP NR specification - may be communicated. Also, scheduling requests requesting resources allocated on the first channel 261 may be communicated. A downlink control channel - e.g., Physical Downlink Control Channel (PDCCH) according to the 3GPP NR specification - is not shown

FIG. 3 illustrates aspects in connection with a carrier 370 of the wireless link 114. FIG. 3 schematically illustrates a BW 380 of the carrier 370. For example, the carrier 370 can operate according to OFDM and can include multiple subcarriers (not illustrated in FIG. 3).

FIG. 3 further illustrates aspects of BWPs 371-372. The BWPs 371 -372, respectively, occupy an associated subtraction of the overall bandwidth 380. For instance, the BWP 372 shares the spectrum with the BWP 373: The BWP 373 has a smaller BW and is arranged overlapping in frequency domain with the BWP 372.

It would be possible that the BWP 372 is assigned to reference UEs and that the BWP 373 is assigned to RedCap UEs. I.e. , the BWP 372 is operated for reference UEs and the BWP 373 is operated for RedCap UEs. This would mean that only Red- Cap UEs such as the RedCap UE 101 access the BWP 373; while only reference UEs such as the reference UE 91 access the BWP 372. As a general rule, allocation of resource elements of the time-frequency grid for transmission of various signals, including PRSs, can be relatively defined with respect to the respective BWP 371 -373. Each BWP 371-373 can be defined as a subset of continuous and contiguous common physical resource blocks (PRBs), each PRB defining a set of resources in the time-frequency grid. As a general rule, each BWP 371 - 373 each can have a unique OFDM numerology.

The UE 91 , 101 generally uses, at each moment in time, a single BWP 371-373. This is the so-called “active BWP”. Messages, e.g., communicated on the PLICCH or PDCCH can be used to switch between BWPs. It would also be possible to use an inactivity timer.

In 3GPP Release 15 four different BWPs are defined, the so-called initial BWP and three other BWP types where each BWP can be configured for a carrier component. The initial BWP or BWPs are configured by broadcast messages, e.g., system information block (SIB). The non-initial BWPs can be configured RRC messages. The initial BWP is used during initial access procedure and the other 3 BWPs are used when operating in a connected mode. An initial BWP does not have a UE-specific configuration and hence, is configured to accommodate all UEs of a given type (e.g., either reference UEs or RedCap UEs). Hence, it is shared between all UEs during initial access. Other BWPs can have UE-specific configurations which can be used during connected mode. Aspects with respect to the connected mode and the initialaccess procedure are explained in connection with FIG. 4.

FIG. 4 illustrates aspects with respect to different modes in which a UE 91 , 101 can operate. FIG. 4 illustrates aspects with respect to a connected mode 401 . In the connected mode 401 , the data connection 189 is established. The UE 91 , 101 is registered at the network.

In an idle mode 402, the data connection 189 is not established. The UE 91 , 101 can transition to the connected mode 401 using an initial access procedure.

Note that generally there can be further modes, e.g., deregistered - where no registry of the UE is kept at the network - or inactive where the UE connectivity is managed by the RAN 111 rather than the CN. Example modes that can be used herein are described in 3GPP TR 38.804 V14.0.0 (2017-03), FIG. 5.5.2-1 for 3GPP NR.

In various modes, in an initial-access procedure 6000 may be used to transition to the connected mode 401 .

To support the initial-access procedure 6000, it is possible to use an initial UL BWP and an initial DL BWP. These initial BWPs may be advertised by the BS 112 in a broadcast message, e.g., a SIB. Thus, a UE - even when not operating in the connected mode 401 - can read the respective configuration of the initial BWPs and use them during the initial access procedure. As explained above, there may be different initial BWPs for different UE categories according to TAB. 1 ; e.g., initial UL and/or DL RedCap-BWPs and initial UL and/or DL reference-BWPs.

FIG. 5 illustrates aspects with respect to finding UL and DL initial BWPs 375, 376. The techniques explained in FIG. 5 are applicable to RedCap-BWPs as well as refer- ence-BWPs. The UL and DL initial BWPs 375, 376 are found by detecting the synchronization signals in the SSB at 6605. The SSB also includes the broadcast message carrying the Master Information Block (MIB). The MIB together with information decoded from synchronization signals points at CORESET#0 that are located at a certain frequency and time offset from the SSB but in direct closer location to the SSB, at 6610. The CORESET#0 includes the scheduling information of SIB-1 , 6615, and thereby indicates the first initial DL BWP 375 that can be used at 6620. By default, the initial DL BWP 375 for initial-access procedure is equal to the bandwidth of CORESET#0. However, in SIB1 , it is possible to override this default configuration. Also, the configuration of the initial UL BWP 376 is provided in SIB1 at 6615.

The initial BWPs 375, 376 can be used in an initial-access procedure, i.e., data can be transmitted or received by the respective UE 91 , 101 on the initial BWPs 375, 376. Details with respect to the initial-access procedure are illustrated in FIG. 6.

FIG. 6 schematically illustrates aspects with respect to an initial-access procedure 6000. FIG. 6 is a signaling diagram of communication between the UE 101 and the BS 112. FIG. 6 specifically illustrates aspects with respect to a contention-based random-access (RA) procedure. The initial-access procedure 6000 includes multiple steps, starting with a RA message 1 (Msg.1 ) 6001 carrying a RA preamble being transmitted from the UE 101 to the BS 112 at 6501 . Prior to this, synchronization between the UE 101 and the BS 112 based on synchronization reference signals, as well as MIB/SIB reception at the UE 101 can take place (not shown).

The RA preamble as used herein may be a pattern or signature. The value of the RA preamble (preamble index) may facilitate distinguishing between different UEs. The RA preamble may be selected from a set of preambles, e.g., 64 or 128 candidate preambles. The different preambles may use orthogonal codes. Generally, the RA preamble does not uniquely identify a UE 101 , but still is used by the UE 101 for some time as device-specific parameter.

Next, at 6502, a DL RA response message 6002 (Msg.2; also referred to as RA Response message, RAR message) is transmitted by the BS 112 and received by the UE 101. This is on an initial DL BWP using both PDCCH and PDSCH. The RAR message 6002 includes an UL grant for resource allocation for one or more physical resource blocks (PRBs) defined in a time-frequency grid of an OFDM carrier (cf. FIG. 2). The RAR message 6002 is addressed to the Radio Network Temporary Identity (RNTI) of the UE 101.

The UE 102 then, at 6503, sends the RA message Msg.3 6003 (Msg.3). This is on an initial UL BWP using PUSCH. The RA message Msg.3 6003 occupies the one or more PRBs allocated by the UL grant of the RAR message 6002. Multiple information elements are included in a TB associated with the RA message Msg.3 6003 that is mapped to the one or more PRBs.

The RA message Msg.3 6003 carries a first information element, namely a RRC connection request 162 or an RRC Connection Resume that includes an identity such as S-TMSI or a Cell Radio Network Temporary Identity (C-RNTI) if available at the UE. This is for setting up the data connection 189 on Layer 3 of a respective transmission protocol stack.

At 6504, the BS 112 responds with a DL RA contention resolution message 6004 (Msg.4) and any potential contention between other UE:s may be resolved. The DL RA contention resolution message 6005 is transmitted on the initial DL BWP 375 (of.

FIG. 5).

The UE 101 can then transmit, on the initial UL BWP 376, a positive acknowledgement or negative acknowledgement of the Msg.4 6004. This acknowledgement is communicated on the PLICCH 262.

If the connection attempt of the UE 101 to the cellular network 100 is successful, the data connection 189 may be established. Then, wireless communication of payload UL data and/or payload DL data along the data connection 189 can commence.

Various techniques disclosed herein are concerned with the appropriate configuration of multiple initial UL BWPs, both for RedCap UEs, as well as for reference UEs. Specifically, co-existence between an initial UL reference-BWP and multiple initial UL RedCap-BWPs is facilitated according to the techniques disclosed herein. However, before these examples according to the disclosure will be explained in detail, reference implementations are discussed in FIG. 7.

FIG. 7 schematically illustrates aspects with respect to reference implementations of initial BWPs 601 , 611-613. Illustrated is an initial UL reference-BWP 601 assigned to reference UEs such as the reference UE 91 (cf. TAB. 1 ). The initial UL reference- BWP 601 includes, adjacent to its upper frequency 685 and its lower frequency 686, resources allocated to the PUCCH 262.

Also illustrated there are three possible implementations of initial UL RedCap-BWPs 611 -613 assigned to RedCap UEs such as the UE 101 . The initial UL RedCap-BWP 611 includes resources allocated to the PUCCH 262 at its upper frequency 685 and at its lower frequency 686. The initial UL RedCap-BWP 612 includes one-sided resources allocated to the PUCCH 262 only at its lower frequency 686; while the initial UL RedCap-BWP 613 includes one-sided resources allocated to the PUCCH 262 at its upper frequency 685 (i.e. , asymmetric allocation of resources allocated to the PUCCH 262).

The center frequencies of the initial UL RedCap-BWPs 611 -613 are all aligned with the center frequency of the initial UL reference-BWP 601 . Thus, resources allocated to the PLISCH 261 of the initial UL reference-BWP 601 are fractioned by the resources allocated to the PLICCH 262 of each one of the initial UL RedCap-BWPs 611-613. This can cause interference, reduced data throughput, and reduce the flexibility resource allocation in the initial UL reference-BWP 601 . Accordingly, the initial UL RedCap-BWPs 611-613 are non-preferred reference implementations.

Also illustrated in FIG. 7 is a further possible implementation of an initial UL RedCap- BWP 614. Here, the upper frequency 685 of the initial UL RedCap-BWP 614 is aligned with the upper frequency 685 of the initial UL reference-BWP 601 . One-sided resources are allocated adjacent to the upper frequency 685 of the initial UL Red- Cap-BWP 614 to the PUCCH 262.

This avoids fractionating of the PUSCH 261 resources of the initial UL reference- BWP 601 ; nonetheless, the one-sided resources allocated to the PUCCH 262 limit the availability capacity for PUCCH data transmissions. Congestions may result. Furthermore, the one-sided resources allocated to the PUSCH 261 also limit the availability capacity for PUSCH transmission.

According to various examples, it is possible to mitigate such and further problems as outlined above in connection with the reference implementations according to each one of the initial UL RedCap-BWPs 611 -614. Strategies for operating initial UL RedCap-BWPs are presented that offer optimized use of resources, thereby minimizing congestions I collisions in PUCCH and PUSCH regions.

According to various examples, it is possible to operate a first UL BWP having a first BW assigned to a first device type (e.g., reference UEs) and, at the same time, operate multiple second initial UL BWPs having one or more second BWs that are smaller than the first BW; the second initial UL BWPs are assigned to as second device type, e.g., RedCap UEs. The second device type can be identified at the cellular NW is not supporting the entire first BW.

By such techniques, it is possible to provide multiple candidate BWPs for the UEs of the UEs of the second device type, thereby supporting smaller BW capabilities at large capacity.

A corresponding scenario is illustrated in FIG. 8. FIG. 8 illustrates aspects with respect to co-existence of multiple initial UL RedCap- BWPs 621 , 622 with a UL reference-BWP 601 , e.g., an initial UL reference-BWP. Also illustrated are the BWs 971 , 975, 976. The BWs 975, 976 of the multiple initial UL RedCap-BWPs 621 , 622 are each smaller than the BW 971 of the initial UL reference BWP 601. Specifically, the RedCap UE 101 is identified at the cellular NW as not supporting the entire BW 971 . This is why the RedCap UE 101 can use the initial UL RedCap-BWPs 621 , 622.

The initial UL RedCap-BWPs 621 , 622 are offset from each other in frequency domain. In the illustrated scenario, a frequency gap 681 is present.

In the illustrated scenario, the multiple initial UL RedCap-BWPs 621 , 622 overlap in frequency domain with the initial UL reference-BWP 601. The upper frequencies 685 of the initial UL reference-BWP 601 and the initial UL RedCap-BWP 621 coincide. Similarly, the lower frequencies 686 of the initial UL reference-BWP 601 and the initial UL RedCap-BWP 622 also coincide.

The initial UL RedCap-BWP 621 includes one-sided resources allocated to PUCCH 262, at its upper edge; and the initial UL RedCap-BWP 622 includes one-sided resources allocated to the PUCCH 262 at its lower edge. Thereby, fragmentation of the PUSCH resources of the initial UL reference-BWP 601 is avoided.

FIG. 9 schematically illustrates the BS 112. The BS 112 includes a processor 1122 and a memory 1123, as well as an interface 1121 via which the processor 1122 can communicate with other nodes and devices. For instance, the interface 1121 could include a radio wireless interface so that the wireless link 114 can be accessed. The processor 1122 can load and execute program code from the memory 1123. Executing the program code causes the processor 1122 to perform techniques as described herein, e.g.: operating multiple initial UL BWPs, e.g., assigned to different device categories; determining and providing to UEs respective configurations of BWPs; determining at least one initial UL RedCap-BWP of multiple initial UL RedCap-BWP based on a usage rule; etc..

FIG. 10 schematically illustrates the RedCap UE 101 (the UE 91 can be configured similarly). The RedCap UE 101 includes a processor 1012 and a memory 1013, as well as an interface 1011 via which the processor 1012 can communicate with other nodes and devices. For instance, the interface 1011 could include a radio wireless interface so that the wireless link 114 can be accessed. The processor 1012 can load and execute program code from the memory 1013. Executing the program code causes the processor 1012 to perform techniques as described herein, e.g.: obtaining a configuration of multiple initial UL BWPs; transmitting UL data on a least one of the multiple initial UL BWP; determining the at least one of the multiple initial UL BWPs based on the usage rule; etc.

FIG. 11 is a flowchart of a method according to various examples. The method of FIG. 11 can be executed by an access node of a communications network. For instance, the method of FIG. 11 could be executed by a BS 112 of a cellular network 100. For instance, the method of FIG. 11 could be executed by the processor 1122 of the BS 112 is illustrated in FIG. 9.

FIG. 11 illustrates aspects in connection with coexistence between reference UEs and RedCap-UEs, cf. TAB. 1 . Specifically, FIG. 11 is associated with a setup in which an UL reference-BWP and multiple initial UL RedCap-BWPs are overlapping in frequency domain. For instance, a scenario is illustrated in FIG. 8 would be possible. This means that usage of resources allocated to the PUCCH 262 can be maximized by using one-sided resources allocated to the PUCCH at the upper and lower frequencies of respective reduced capability initial UL BWPs; while, at the same time fragmentation of PUSCH of the initial UL reference BWP is avoided. Such fragmentation can arise because data on the PUCCH may include scheduling requests from the RedCap-UEs; such scheduling requests are not announced to the network beforehand; thus pre-scheduled data on the PUSCH may suffer from interference from scheduling requests on the PUCCH.

In FIG. 11 , optional boxes are labeled with dashed lines.

For instance, the method of FIG. 11 could be applicable to a context of a RedCap UE accessing a cellular NW for the first time. Another context would be SIB update.

In FIG. 11 : box 5005, it is possible to obtain an indication of a capability of a RedCap- UE such as the RedCap UE 101. For instance, respective message may be received from the RedCap-UE. A RRC message may be received on PUSCH. It would also be possible to lookup the capability in a repository of the communications NW, e.g., at the AMF 131 . Here, a respective UE context may list a respective capability.

For instance, it would be possible that the capability indicates that the wireless communication device belongs to the RedCap type (cf. TAB. 1 ).

Alternatively or additionally, it would be possible that the capability indicates that the RedCap UE can transmit UL data using frequency hopping across multiple initial UL BWPs.

At box 5010, it would then be possible to operate a first UL BWP for a first device type - e.g., reference UEs - and operating multiple second initial UL BWPs for a second device type - e.g., RedCap UEs. In other words, the UL reference-BWP may be assigned to/reserved for/allocated to/configured for use by reference UEs; while the multiple initial UL RedCap-BWPs may be assigned to/reserved/allocated to/configured for use by for RedCap UEs.

This means that, as a general rule, a reference-BWP is to be used by reference UEs. A RedCap-BWP is to be used by RedCap UEs. Specifically, an initial UL RedCap- BWP is to be used by RedCap UEs during an initial access procedure for UL data, e.g., control signals on PUCCH and/or messages on PUSCH.

Operating (i.e. , activating or supporting) the first UL BWP can include determining a respective configuration and indicating that configuration to the UEs of the first device type. Operating the first UL BWP can include receiving data on the first UL BWP in accordance with the configuration, i.e., using the first UL BWP.

Operating (i.e., activating or supporting) the multiple second initial UL BWPs can include determining respective configurations and indicating these configurations to the UEs of the second device type. Operating the second UL BWPs can include receiving data on the second UL BWPs in accordance with the configuration, i.e., using these second UL BWPs.

Thus, in principle a RedCap-UE may be eligible for accessing any one of the multiple initial UL RedCap-BWPs. However, according to various examples, it is possible to determine at least one of the multiple initial UL RedCap-BWPs. For instance, a selection process may be executed. Here, a usage rule may be considered. Then, rather than accessing an arbitrary one of the multiple initial UL RedCap-BWPs, the Red- Cap-LIE may access specifically the at least one of the multiple reduced capability initial UL BWPs.

Each one of the multiple initial UL RedCap-BWPs may be associated with one and the same initial DL BWP. I.e. , PDCCH on the initial DL BWP may carry DCI for PUSCH of each one of the multiple initial UL RedCap-BWPs.

At box 5015, when operating the multiple initial UL RedCap-BWPs, it is optionally possible to transmit a broadcast message - e.g., a SIB - that includes a configuration for the multiple initial UL RedCap-BWPs.

In other options, it would be possible that a broadcast message is transmitted that is indicative of a configuration of the UL reference-BWP, i.e., defines the UL reference- BWP. Then, it would be possible that the configuration of the multiple initial UL RedCap-BWPs is linked to the configuration of the UL reference-BWP. I.e., it would be possible that a RedCap-UE derives the configuration of the multiple initial UL RedCap-BWPs from the configuration of the UL reference-BWP. For instance, there could be a fixed rule that specifies the frequency arrangement of the multiple initial UL RedCap-BWPs with respect to the UL reference-BWP.

Then, it would be optionally possible, at box 5020, to determine at least one initial UL RedCap-BWP from the multiple initial UL RedCap-BWPs. I.e., it would be possible to narrow down which at least one of the multiple initial UL RedCap-BWPs will be used by a given UE. A selection process from multiple candidates can be implemented. A usage rule may be used. The usage rule may be shared between the RedCap-UE and the cellular network, i.e., control signaling indicative of the usage rule may be used. This may occur prior to box 5020, i.e., the usage rule can be pre-configured. In some scenarios, the usage rule may be predefined according to the communication protocol. The usage rule may specify how to determine at least one of the multiple initial UL RedCap-BWPs depending on the circumstances, e.g., a NW state, a device state, etc.

For instance, box 5020 could be executed in response to detecting an initial-access procedure of a RedCap-UE. For instance, a RA preamble may be received. The selection may depend on the RA preamble. It is not required in all scenarios that at least one of the multiple initial UL RedCap- BWPs is determined. A selection process may not be required. In some scenarios, it would be possible that the access node simply monitors, at box 5025, all of the multiple initial UL RedCap-BWPs and then detects the particular one of the multiple initial UL RedCap-BWPs which is used by the UE to transmit UL data.

In any case, at box 5025, it would be possible to monitor at least one of the multiple initial UL RedCap-BWPs. For instance, PUCCH may be monitored for transmissions of acknowledgements (cf. FIG. 6: 6505). “Monitoring” can relate to attempting to receive, e.g., making decoding attempts.

In some scenarios, it would be possible to monitor two or more of the multiple initial UL RedCap-BWPs in accordance with frequency hopping between the two or more multiple initial UL RedCap-BWPs used by the RedCap UE. This can be in accordance with the respective capability as indicated by the RedCap-UE at box 5005.

FIG. 12 is a flowchart of a method according to various examples. The method of FIG. 12 can be executed by a UE that is connectable to a communications network, e.g., a cellular NW. Example contexts would relate to a first-time access to a cellular NW or retransition to connected mode after operating in idle mode or inactive mode. For instance, the method of FIG. 12 may be executed by a RedCap-UE (cf. TAB. 1 ). For instance, the method of FIG. 12 could be executed by the UE 101. More specifically, it would be possible that the method of FIG. 12 is executed by the processor 1012 upon loading and executing program code from the memory 1013.

FIG. 12 illustrates aspects in connection with the co-existence between reference- UEs and RedCap-UEs, cf. TAB. 1.

FIG. 12 is a method interrelated to the method according to FIG. 11 .

In FIG. 12, optional boxes are labeled with dashed lines.

In FIG. 12, box 5105, an indication of a capability of the UE can be provided to the cellular network. Box 5105 is interrelated to box 5005. Aspects explained in connection with the capability in connection with box 5005 are also applicable to box 5105. Next, at box 5115, a configuration of multiple initial UL RedCap-UEs is obtained.

There are various options available for implementing box 5115. Some of these options are summarized below in TAB. 2.

TAB. 2: Various options for implementing a configuration of multiple initial UL Red- Cap-BWPs. The options can be combined with each other.

Next, at box 5120, at least one of the multiple initial UL RedCap-BWPs that are operated in a cell is determined. As a general rule, the RedCap-UE may only be capable of accessing a single one of the multiple initial UL RedCap-BWPs at a given moment in time. Hence, it may be required to determine which one of the multiple initial UL RedCap-BWPs to access.

For instance, where frequency hopping is employed, it would be possible to deter- mine a frequency-hopping sequence of subsequently using the multiple initial UL RedCap-BWPs, or, more generally, a first frequency of a frequency-hopping sequence (of the multiple initial UL RedCap-BWPs that are initially accessed using the frequency hopping).

When determining the at least one of the multiple initial UL RedCap-BWPs, it is pos- sible to take into account a usage rule. Various options are available for implementing the usage rule in some scenarios are summarized below in connection with TAB.

3.

TAB. 3: Various options for an implementation of the usage rule. It would be possible that the usage rule includes multiple such options. For instance, examples l-lll are based on device-specific parameters. These are parameters that can vary from UE to UE. These parameters can be associated at least for some time with the respective UE. By considering such device-specific parameters, it is possible to distribute load between different ones of the multiple initial UL RedCap-BWPs. Similar load-balancing can be achieved by a randomized decision process according to example IV. TAB. 3 includes only examples; other examples can be used, and usage rules may be defined to provide even/fair load-balancing between the initial UL RedCap-BWPs.

The usage rule may be fixedly predefined according to the communication protocol. It would also be possible that the usage rule is shared between the UE and the cellular network. I.e. , it would be possible that the UE selects the usage rule and informs the cellular network accordingly, or vice versa. For instance, it would be possible that the usage rule as indicated by at least one broadcast message from the cellular network. For instance, it would be possible that the usage rule is indicated along with the configuration, as discussed in connection with box 5115.

Then, once the at least one of the multiple initial UL RedCap-BWPs has been determined, it is possible, at box 5125, to transmit on the determined at least one of the multiple initial UL RedCap-BWPs. This can include, e.g., a PUCCH transmission, e.g., of a positive or negative acknowledgement (cf. FIG. 6: 6505). Where no frequency hopping is employed, a single one of the multiple initial UL RedCap-BWPs is determined and used for transmission of data. Where two or more of the multiple initial UL RedCap-BWPs are determined, frequency hopping is employed. For instance, it would be possible to switch a frequency from a first one of the multiple initial UL RedCap-BWPs to a second one of the multiple initial UL RedCap-BWPs while trans- mitting a given part of the UL data, e.g., a given part of the UL data encoding an acknowledgment message or another message. In other words, it would be possible to switch between adjacent symbols encoding a contiguous fraction of data, e.g., a Layer 2 or Layer 3 message. A certain switching time may be considered, i.e. , it would be possible to accommodate for a respective time gap. In further scenarios, it would also be possible to switch between subsequent parts of UL data, e.g., according different messages, e.g., a message on PUCCH and the further message on the PUSCH. Further example, a message on PUSCH and the further message is the retransmitted PUSCH.

Frequency hopping can be explicitly activated or deactivated. I.e., it would be possible that the cellular network informs the UE (or vice versa) whether to transmit the UL data using frequency hopping.

As a general rule, each frequency hop could be on finer granularity in time domain e.g., slot or a few symbols. The frequency hops are related to a minor switch delay to let the local oscillator retune for the different center of the BWP.

Summarizing, techniques have been disclosed of configuring to initial UL BWP for BW-limited devices, i.e., RedCap UEs. A RedCap UE can use one of the two initial UL BWPs at a time. Frequency hopping can be employed.

For the initial ULRedCap-BWPs, it is possible to reuse a section of a UL reference BWP assigned to reference UEs (i.e., non-bandwidth-limited device). Hence, the two initial UL RedCap-BWPs may be allocated at the edges of the UL reference-BWP. Thereby, the usage of resources allocated to the UL control channel can be maximized, because the resources can be allocated at the edges of the reference UL BWP.

A configuration of the initial UL RedCap-BWPs can be provided in a broadcast message such as the system information block, e.g., SIB1. To save control signaling overhead, common configuration information elements can be used that are applicable to all initial UL RedCap BWPs. Information elements can also be used that are specific for each one of the initial UL RedCap BWPs, e.g., frequency resource information.

A usage rule - that may also be referred to as access-control rule - can be provided, e.g., as part of the configuration. For example, to ensure that two initial UL RedCap BWPs are equally used by the RedCap UEs, the usage rule can enforce load-balancing.

The configuration can also be indicative of whether a BS supports only a single initial UL RedCap BWP or multiple initial UL RedCap BWPs.

The configuration can also be indicative of whether a base station is capable of handling frequency-hopping between multiple initial UL RedCap BWPs.

A RedCap-UE may provide a capability signaling whether it can only use a single initial UL RedCap-BWP or two or more initial UL RedCap-BWPs (e.g., for frequency hopping purpose).

A Redcap-UE that can only support a single initial UL RedCap-BWP will access a single initial UL RedCap-BWP according to a usage rule, for PUSCH and PUCCH data transmission.

A Redcap-UE that can support multiple initial UL RedCap-BWPs may have access to multiple initial UL RedCap-BWPs (but one at a time). It includes accessing both PUSCH and PUCCH channel and performing frequency hopping for both channels.

Although the invention has been shown and described with respect to certain preferred embodiments, equivalents and modifications will occur to others skilled in the art upon the reading and understanding of the specification. The present invention includes all such equivalents and modifications and is limited only by the scope of the appended claims.

For illustration, various examples have been disclosed in connection with initial UL BWPs, but similar techniques may be applicable to initial DL BWPs.

For further illustration, various examples have been described in the context of initial BWPs used for transmitting data of an initial-access procedure. However, the strategies disclosed herein can also be applicable to other BWPs that are specifically configured and active after the initial-access procedure.