WO2022098284A1

WO2022098284A1 - Coverage recovery for reduced capability wireless devices

Info

Publication number: WO2022098284A1
Application number: PCT/SE2021/051100
Authority: WO
Inventors: Yi-Pin Eric Wang; Saeedeh MOLOUDI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-11-08
Filing date: 2021-11-04
Publication date: 2022-05-12

Abstract

A network node (16, 16a, 16b, 16c) receives a message from a wireless device (22, 22a, 22b) as part of a random access procedure, and transmits a Msg4 message to the wireless device as part of the random access procedure. The Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.

Description

COVERAGE RECOVERY FOR REDUCED CAPABILITY WIRELESS DEVICES

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to coverage recovery solutions for reduced capability wireless devices.

BACKGROUND

The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.

FIG. 1 illustrates a 4-step contention-based random access (CBRA) procedure used in NR.

• Step 1 : The WD initiates the random access procedure by transmitting a random-access preamble (also referred to as message 1 or Msgl) to a network node using a physical random-access channel (PRACH).

• Step 2: The network node responds to the preamble by transmitting a random-access response (also referred to as message 2 or Msg2) to the WD. The random access-response (RAR) includes an uplink grant that schedules a physical uplink shared channel (PUSCH).

• Step 3: After receiving the RAR, the WD transmits a PUSCH transmission to the network node in accordance with the uplink grant. This PUSCH transmission is also referred to as message 3 or Msg3.

• Step 4: The network node responds to the PUSCH transmission by transmitting a contention resolution message (also referred to as message 4 or Msg4) to the WD.

For critical machine type communication (cMTC) support, ultra-reliable low latency communications (URLLC) was introduced in 3 GPP Release 15 for both LTE and NR. NR URLLC is further enhanced in 3 GPP Release 16 within the enhanced URLLC (eURLLC) and Industrial Internet of Things (loT) work items. For massive machine type communications (mMTC) and low power wide area (LPWA) support, 3 GPP introduced both narrowband Internet-of-Things (NB-IoT) and long term evolution for machine-type communication (LTE-MTC, or LTE-M) in 3GPP Release 13. These technologies have been further enhanced through all releases up until and including the ongoing 3 GPP Release 16 work.

NR (New Radio) was introduced in 3 GPP Release 15 and focused mainly on enhanced mobile broadband (eMBB) and cMTC. For 3GPP Release 17, however, an NR WD type with lower capabilities may be introduced since it is supported and proposed by many companies. The intention is to have a reduced capability version of NR devices, i.e., Reduced capability NR devices (NR-RedCap), which is middle-end, filling the gap between eMBB NR and NB- loT/LTE-M. This is to provide more efficient inband operation with URLLC in industrial use cases.

Low-cost or low-complexity WD implementation is needed for the 5G system, e.g., for massive industrial sensor deployments or wearables. Currently, a NR-RedCap (Reduced capability NR device) is used as the running name for the discussion of such low-complexity WDs in 3 GPP. NR-RedCap is intended for use cases that do not require a device to support full-fledged NR capability and International Mobile Telecommunications (IMT)-2020 performance requirements. For example, the data rate does not need to reach above 1 Gbps (gigabits per second), and the latency does not need to be as low as 1 ms (milliseconds). By relaxing the data rate and latency targets, NR-RedCap allows low-cost or low-complexity WD implementation.

Based on a study item (RP-193238, New SID on support of reduced capability NR devices, 3GPP TSGRAN Meeting #86, December 9th - 12th, 2019) on the support of NR-RedCap devices for use cases such as industrial wireless sensors, video surveillance, and wearables, lower device cost and complexity as compared to high-end eMBB and URLLC devices of 3 GPP Releases 15 and 16, are among the requirements for these three use cases.

Based on the study item on RedCap WDs (RP-193238, New SID on support of reduced capability NR devices, 3GPP TSG RAN Meeting #86, December 9th - 12th, 2019), certain cost and complexity reduction features have been considered, including the reduction of the number of WD antennas and WD bandwidth. Thus, in one of the study item objectives of the 3 GPP Release 17, RedCap Study Item (SI) (RP-193238, New SID on support of reduced capability NR devices, 3GPP TSGRAN Meeting #86, December 9th - 12th, 2019), it is considered to

“Study functionality that will enable the performance degradation of such complexity reduction to be mitigated or limited, including [RANI ]:

• Coverage recovery to compensate for potential coverage reduction due to the device complexity reduction. ”

SUMMARY

A first aspect provides embodiments of a method implemented in a network node. The method comprises receiving a message from a wireless device as part of a random access procedure, and transmitting a Msg4 message to the wireless device as part of the random access procedure. The Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.

Corresponding embodiments of a network node are also provided.

A second aspect provides embodiments of method implemented in a wireless device. The method comprises transmitting a message to a network node as part of a random access procedure. The transmitted message indicates whether the wireless device is a reduced capability wireless device. The method also comprises receiving a Msg4 message from the network node as part of the random access procedure. The Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

Corresponding embodiments of a wireless device are also provided.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG. 1 illustrates a random access procedure; FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 8 is a flowchart of an exemplary process in a network node for coverage recovery solutions for RedCap-Msg4;

FIG. 9 is a flowchart of an exemplary process in a network node for coverage recovery; and

FIG. 10 is a flowchart of an exemplary process in a wireless device for coverage recovery.

DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to coverage recovery solutions for Msg4 for reduced capability wireless devices (also referred to herein as RedCap-Msg4). Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide coverage recovery solutions for Msg4 for reduced capability wireless devices. Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN. The WD 22 may also be in communication with another WD in what is sometimes called sidelink communication. Note that some or all of the WDs 22 may be reduced capability WDs 22.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 may for example be configured to include a MCS selector 32 which is configured to select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD, when the WD is a reduced capability WD.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include the MCS selector unit 32 configured to select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD, when the WD is a reduced capability WD.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

In FIG. 3, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 2 and 3 show various “units” such as MCS selector 32 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08). FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block SI 20). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block SI 22). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block SI 24). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 26).

FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block SI 28). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

As described above, reduced capability (RedCap) wireless devices (WD) may be introduced in NR. One potential consequence of device cost and complexity reductions associated with reduced capability wireless devices is coverage loss. The impact of the complexity reduction is not identical on different physical channels, so the levels of the needed coverage recovery are likely different for different physical channels. The levels of the needed coverage recovery are also likely different for different deployment scenarios.

As one of the complexity reduction features is reducing the number of WD receive (Rx) antennas, the impact of the complexity reduction may be more considerable on coverage of the downlink (DL) channels and messages than that of the uplink (UL) channels. This DL coverage situation may become even more challenging in a micro-cell where the NR base station (gNB) power level is much lower compared to a macro cell. Likewise, DL coverage is more challenging in an FR2 band due to a lower network node power level that is allowed.

Msg4 is one of the DL random-access procedure messages whose coverage may be considerably affected by device complexity reduction and potentially can be a coverage limiting channel.

Reducing the number of the WD receive antennas for RedCap WDs, may have a considerable impact on the coverage of Msg4 for RedCap WDs (also referred to herein as RedCap-Msg4). Currently, there is not any coverage recovery solution that compensates for the coverage loss for Msg4 for RedCap WDs.

Some embodiments advantageously provide methods, systems, and apparatuses for coverage recovery solutions for Msg4 for RedCap WDs.

In some embodiments, the network node (for example, a gNB) learns from UL message 1 on the physical random access channel (PRACH) or UL message 3 on the PRACH whether the WD is a RedCap device or NR WD. Therefore, the network node can use this knowledge to enhance the coverage for RedCap-Msg4 in two ways: 1) for RedCap WDs, the network node can use a modulation and coding scheme (MCS) table in which the MCS indices provide smaller spectral efficiencies and code rates and/or 2) the network node can consider new settings between transport block size (TBS) and the number of physical resource blocks (PRBs) for RedCap WDs.

In some embodiments, the coverage loss due to the complexity reduction can be at least partially compensated for RedCap-Msg4.

FIG. 8 is a flowchart of an exemplary process in a network node 16 for coverage recovery solutions for RedCap-Msg4. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the MCS Selector 32), processor 70, radio interface 62 and-/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to determine when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD (Block SI 34). The process also includes, when the WD is a reduced capability WD, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD (Block SI 36).

FIG. 9 is a flowchart of an exemplary process in a network node 16 for coverage recovery. The network node receives 901 a message from a wireless device 22 as part of a random access procedure, and transmits 902 a Msg4 message to the wireless device 16 as part of the random access procedure. The Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device 22 is a reduced capability wireless device than if the received message does not indicate that the wireless device 22 is a reduced capability wireless device.

FIG. 10 is a flowchart of an exemplary process in a wireless device 22 for coverage recovery. The wireless device 22 transmits 1001 a message to a network node 16 as part of a random access procedure. The transmitted message indicates whether the wireless device 22 is a reduced capability wireless device. The wireless device 22 receives 1002 a Msg4 message from the network node 16 as part of the random access procedure. The Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device 22 is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device 22 is a reduced capability wireless device. Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for coverage recovery solutions for Msg4 for reduced capability wireless devices.

One of the steps in determining the transport block size (TBS) is computing the so-called intermediate number of information bits, N_inf_O, as follows: info ~ R_ER Qm^V’ wherein R, Q_m, and v are code rate, modulation order, and the number of transmission layers, respectively. The code rate and modulation order depend on the MCS index and can be looked up from one of the tables 5.1.3.1-1, 5.1.3.1-2 and 5.1.3.1-3 in 3GPP TS 38.214, vl6.3.0, “NR; Physical layer procedures for data (Release 16)”. N_RE is the number of the available resource elements in a slot, and can be computed as:

]\T ' — i\jRB i\jsh _ ]\jPRB _ i\jPRB

‘ ' RE ~ ^l sc ^l sym ^l DMRS ^JV oh ’

NRE ⁼ min(156, /V_R£) n_PRB,

and n_PRB show respectively the number of the subcarriers in a PRB, the number of orthogonal frequency division multiplexed (OFDM) symbols in a slot, the number of resource elements (REs) belong to demodulation reference signal (DM-RS) in a physical resource block (PRB), the overhead and the total number of the available PRBs.

For RedCap WDs 22, to improve the coverage of the DL physical channels including Msg2 and Msg4, the TBS and PRB settings can be adapted to reduce the effective code rate in computing the N_inf₀ or, in other words, considering transmitting a smaller number of information bits for a given number of PRBs.

A RedCap WD signals its WD type and identification in Msgl or Msg3. Therefore, the network node 16 can use this knowledge to transmit Msg4 to the RedCap WD 22 with smaller effective code rate than that of the NR WDs 22. In some embodiments, methods are proposed, based on which the effective code rate can be reduced specifically for transmission of Msg 4 to RedCap WDs 22. Different embodiments can be used separately or in combination with each other. Among the above mentioned MCS tables 5.1.3.1-1, 5.1.3.1-2 and 5.1.3.1-3 in 3GPP TS 38.214, vl6.3.0, “NR; Physical layer procedures for data (Release 16)”, one table may provide lower code rates and lower spectral efficiency. In some embodiments, the network node 16 may, after receiving Msg3 and identifying the WD 22 as a RedCap WD 22, consider using MCS indices from the table that provides smaller code rates.

In another embodiment, a smaller TBS can be assigned to a given MCS and a given number of PRBs, by considering a TBS scaling factor in computing N_inf₀ as: info ~ RER Qm^v-

In some embodiments, the scaling factor, S, can be a constant value for RedCap WDs 22. In an alternative embodiment, the scaling factor, S, can be considered to be equal to that used in an earlier message, Msg2. In another embodiment, using a transport block (TB) scaling field in the downlink control information (DCI), the scaling factor, S, can be selected from a table, for example from the following Table 5.1.3.2-2 of the 3GPP Technical Standard (TS) 38.214, Release 16.

In an alternative embodiment, a new scaling factor table can be considered specifically for RedCap WDs 22, including new values for S. As an non-limiting example:

In some embodiments, the scaling factor, S, can be parameterized as a function of the overall number of available PRBs, Ng^^B, and the number of PRBs considered for NR WD Msg4, N^^RB ₄. s an non-limiting example:

In some embodiments, the network node 16 recognizes the RedCap WDs 22 by Msgl or Msg3. Therefore, the network node 16 can use this knowledge to improve the coverage of RedCap- Msg4. When Msgl or Msg3 indicates to the network node 16 that the WD 22 is a reduced capability WD 22 (RedCap WD), the network node 16 can transmit the RedCap-Msg4 with a smaller effective code rate than that of the normal NR WDs 22.

According to one aspect, a network node 16 is configured to communicate with a wireless device (WD) 22. The network node 16 includes a radio interface 62 and/or processing circuitry 68 configured to: determine when a first message received from the WD 22 on a physical random access channel (PRACH) indicates that the WD 22 is a reduced capability WD 22; and when the WD 22 is a reduced capability WD 22, select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD 22.

According to this aspect, in some embodiments, the first message is a New Radio (NR) reduced capability Msgl or Msg3. In some embodiments, a transport block size (TBS) is determined based at least in part on the smaller coding rate. In some embodiments, the processing circuitry 68 is further configured to assign a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits. In some embodiments, the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.

According to another aspect, a method implemented in a network node 16 includes determining when a first message received from the WD 22 on a physical random access channel (PRACH) indicates that the WD 22 is a reduced capability WD 22, and when the WD 22 is a reduced capability WD 22, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD 22. According to this aspect, in some embodiments, the first message is a New Radio (NR) reduced capability Msgl or Msg3. In some embodiments, a transport block size (TBS) is determined based at least in part on the smaller coding rate. In some embodiments, the method further includes assigning a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits. In some embodiments, the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Below are some example embodiments:

Embodiment Al . A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD; and when the WD is a reduced capability WD, select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD.

Embodiment A2. The network node of Embodiment Al, wherein the first message is a New Radio (NR) reduced capability Msgl or Msg3.

Embodiment A3. The network node of any of Embodiments Al and A2, wherein a transport block size (TBS) is determined based at least in part on the smaller coding rate.

Embodiment A4. The network node of any of Embodiments Al and A2, wherein the processing circuitry is further configured to assign a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.

Embodiment A5. The network node of any of Embodiments A1-A4, wherein the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.

Embodiment B 1. A method implemented in a network node, the method comprising: determining when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD; and when the WD is a reduced capability WD, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD.

Embodiment B2. The method of Embodiment Bl, wherein the first message is a New Radio (NR) reduced capability Msgl or Msg3.

Embodiment B3. The method of any of Embodiments Bl and B2, wherein a transport block size (TBS) is determined based at least in part on the smaller coding rate.

Embodiment B4. The method of any of Embodiments Bl and B2, further comprising assigning a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.

Embodiment B5. The method of any of Embodiments Bl -B4, wherein the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Claims

1. A method implemented in a network node (16), the method comprising: receiving (901) a message from a wireless device (22) as part of a random access procedure; and transmitting (902) a Msg4 message to the wireless device as part of the random access procedure, wherein the Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.

2. The method of claim 1, wherein the received message is a Msgl message or a Msg3 message.

3. The method of any of the preceding claims, wherein the Msg4 message is transmitted with lower effective code rate for enhancing coverage of the Msg4 message.

4. The method of any of the preceding claims, wherein a modulation and coding scheme, MCS, index table used for the Msg4 message if the received message indicates that the wireless device is a reduced capability wireless device provides lower code rates than a MCS index table used for the Msg4 message if the received message does not indicate that the wireless device is a reduced capability wireless device.

5. The method of any of the preceding claims, further comprising: determining a transmission block size, TBS, for the Msg4 message for a modulation and coding scheme, MCS, and a number of physical resource blocks, wherein, if the received message indicates that the wireless device is a reduced capability wireless device, determining the TBS includes applying a scaling factor compared to if the received message does not indicate that the wireless device is a reduced capability wireless device.

25

6. The method of claim 5, wherein, if the received message indicates that the wireless device is a reduced capability wireless device, the scaling factor is used to determine an intermediate number of information bits.

7. The method of claim 6, wherein info ~ RER Qm^v- if the received message indicates that the wireless device is a reduced capability wireless device, and info ~ ER Q_mV, if the received message does not indicate that the wireless device is a reduced capability wireless device, wherein N_inf₀ is the intermediate number of information bits, N_RE is a number of available resource elements in a slot, R is a code rate, Q_m is a modulation order, v is a number of transmission layers, and S is the scaling factor.

8. The method of any of claims 5-7, wherein a transport block, TB, scaling field in downlink control information, DCI, indicates selection of the scaling factor from a table.

9. The method of claim 8, wherein the table is the same table as used for a scaling factor for a Msg2 message.

10. The method of any of claims 5-8, wherein the scaling factor is the same scaling factor as used for a Msg2 message.

11. The method of claim 8, wherein the table is different than a table used for a scaling factor for Msg2.

12. The method of any of claims 5-11, wherein the scaling factor is 0.1 or 0.25 or 0.3 or 0.5 or 0.7.

13. The method of any of claims 5-7, wherein the scaling factor is parameterized as a function of an overall number of available physical resource blocks, PRBs, and a number of PRBs considered for a Msg4 message for reduced capability wireless devices.

14. The method of claim 13, wherein

wherein S is the scaling factor, N^sg4 is the number of PRBs considered for a Msg4 message for reduced capability wireless devices, and

is the overall number of available PRBs.

15. The method of any of the preceding claims, wherein the wireless device is a reduced capability, RedCap, wireless device.

16. The method of any of the preceding claims, wherein the wirelessed device has reduced capabilities compared to New Radio (NR) Release 15 wireless devices.

17. The method of claim 16, wherein the reduced capabilities include: reduced number of antennas and/or reduced bandwidth.

18. The method of any of claims 16-17, wherein the reduced capabilities include: reduced data rate; and/or higher latency.

19. A network node (16) configured to communicate with a wireless device (22), WD, the network node being configured to: receive a message from the wireless device as part of a random access procedure; and transmit a Msg4 message to the wireless device as part of the random access procedure, wherein the Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.

20. The network node of claim 19, configured to perform the method of any of claims 2-18.

21. A network node (16) configured to communicate with a wireless device (22), the network node comprising a radio interface (62) and/or processing circuitry (68) configured to: receive a message from the wireless device as part of a random access procedure; and transmit a Msg4 message to the wireless device as part of the random access procedure, wherein the Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.

22. The network node of claim 21, wherein the radio interface and/or processing circuitry is configured to perform the method of any of claims 2-18.

23. A method implemented in a wireless device (22), the method comprising: transmitting (1001) a message to a network node (16) as part of a random access procedure, the transmitted message indicating whether the wireless device is a reduced capability wireless device; and receiving (1002) a Msg4 message from the network node as part of the random access procedure, wherein the Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

24. The method of claim 23, wherein the transmitted message is a Msgl message or a Msg3 message.

28

25. The method of any of claims 23-24, wherein the Msg4 message has lower effective code rate for enhancing coverage of the Msg4 message.

26. The method of any of claims 23-25, wherein a modulation and coding scheme, MCS, index table used for the Msg4 message if the transmitted message indicates that the wireless device is a reduced capability wireless device provides lower code rates than a MCS index table used for the Msg4 message if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

27. The method of any of claims 23-26, further comprising: determining a transmission block size, TBS, for the Msg4 message for a modulation and coding scheme, MCS, and a number of physical resource blocks, wherein, if the transmitted message indicates that the wireless device is a reduced capability wireless device, determining the TBS includes applying a scaling factor compared to if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

28. The method of claim 27, wherein the scaling factor is used to determine an intermediate number of information bits.

29. The method of claim 28, wherein info ~ RER Qm^v- if the transmitted message indicates that the wireless device is a reduced capability wireless device, and info ~ NRER Qm^v> if the transmitted message does not indicate that the wireless device is a reduced capability wireless device,

29 wherein N_inf₀ is the intermediate number of information bits, N_RE is a number of available resource elements in a slot, R is a code rate, Q_m is a modulation order, v is a number of transmission layers, and S is the scaling factor.

30. The method of any of claims 27-29, wherein a transport block, TB, scaling field in downlink control information, DCI, indicates selection of the scaling factor from a table.

31. The method of claim 30, wherein the table is the same table as used for a scaling factor for a Msg2 message.

32. The method of any of claims 27-31, wherein the scaling factor is the same scaling factor as used for a Msg2 message.

33. The method of claim 30, wherein the table is different than a table used for a scaling factor for a Msg2 message.

34. The method of any of claims 27-33, wherein the scaling factor is 0.1 or 0.25 or 0.3 or 0.5 or 0.7.

35. The method of any of claims 27-34, wherein the scaling factor is parameterized as a function of an overall number of available physical resource blocks, PRBs, and a number of PRBs considered for a Msg4 message for reduced capability wireless devices.

36. The method of claim 35, wherein

wherein S is the scaling factor, N^g₄ is the number of PRBs considered for a Msg4 message for reduced capability wireless devices, and N_E^^B is the overall number of available PRBs.

30

37. The method of any of claims 23-36, wherein the wireless device is a reduced capability, RedCap, wireless device.

38. The method of any of claims 23-37, wherein the wirelessed device has reduced capabilities compared to New Radio (NR) Release 15 wireless devices.

39. The method of claim 38, wherein the reduced capabilities include: reduced number of antennas and/or reduced bandwidth.

40. The method of any of claims 38-39, wherein the reduced capabilities include: reduced data rate; and/or higher latency.

41. A wireless device (22) configured to communicate with a network node (16), the wireless device being configured to: transmit a message to the network node as part of a random access procedure, the transmitted message indicating whether the wireless device is a reduced capability wireless device; and receive a Msg4 message from the network node as part of the random access procedure, wherein the Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

42. The wireless device of claim 41, configured to perform the method of any of claims 24-40.

43. A wireless device (22) configured to communicate with a network node (16), the wireless device comprising a radio interface (82) and/or processing circuitry (84) configured to: transmit a message to the network node as part of a random access procedure, the transmitted message indicating whether the wireless device is a reduced capability wireless device; and

31 receive a Msg4 message from the network node as part of the random access procedure, wherein the Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.

44. The wireless device of claim 43, wherein the radio interface and/or processing circuitry is configured to perform the method of any of claims 24-40.

32