RANDOM ACCESS RESPONSE SCHEMES FOR ENHANCED REDUCED CAPABILITY (REDCAP) USER EQUIPMENT

Methods, systems, and devices for wireless communication are described. A first network node of a first type of UE may receive a control message indicating one or more PRACH resources to be used for random access of a second network node. Each of the one or more PRACH resources being associated with a respective one or more user equipment (UE) types. The first network node may determine that none of the indicated PRACH resources are associated with the first type of UE. The first network node may select a PRACH resource from the indicated PRACH resources in accordance with a ranking for PRACH resource selection. The first network node may transmit a random access preamble to the second network node via the selected PRACH resource.

INTRODUCTION

The following relates to wireless communications pertaining to random access response schemes for enhanced reduced capability (eRedCap) user equipment (UEs).

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support random access response schemes for enhanced reduced capability (eRedCap) user equipment (UEs). For example, the described techniques provide for receiving, at a first network node, a random access response from a second network node. The first network node may receive the random access response during a random access window associated with a random access request by the first network node. In some examples, the first network node may determine that the random access response is associated with a first UE type. The first UE type may be an enhanced RedCap (eRedCap) UE type. The first network node may decode a transport block of the random access response based on the determination and based on the first network node being the first UE type.

A method of wireless communication performed by a first network node is described. The method may include receiving a control message indicating one or more physical random access channel (PRACH) resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types, determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources, and transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

A first network node is described. The first network node may include a processing system configured to receive a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types, determine that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, select, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources, and transmit the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

Another first network node is described. The first network node may include means for receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types, means for determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, means for selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources, and means for transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

A non-transitory computer-readable medium having code for wireless communication stored thereon is described. The code, when executed by a network node, causes the network node to receive a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types, determine that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, select, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources, and transmit the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes PRACH resources associated with a second UE type when none of the one or more PRACH resources included in the control message may be associated with the first UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes a default PRACH resource when none of the one or more PRACH resources included in the control message may be associated with the first UE type and none of the one or more PRACH resources included in the control message may be associated with the second UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes PRACH resources associated with a third UE type when none of the one or more PRACH resources included in the control message may be associated with the first UE type and none of the one or more PRACH resources included in the control message may be associated with the second UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the second UE type may be a RedCap UE type and the third UE type may be an enhanced mobile broadband (eMBB) UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the first UE type may be associated with a first maximum bandwidth processing capability that may be lower than a second maximum bandwidth processing capability associated with eMBB UEs.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

Some examples of the method, first network nodes, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second control message indicating the ranking for the PRACH resource selection.

A method of wireless communication performed by a first network node is described. The method may include receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types, determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts, and transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

A first network node is described. The first network node may include a processing system configured to receive a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types, determine that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, select, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts, and transmit a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

Another first network node is described. The first network node may include means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types, means for determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, means for selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts, and means for transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

A non-transitory computer-readable medium having code for wireless communication stored thereon is described. The code, when executed by a network node, causes the network node to receive a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types, determine that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type, select, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts, and transmit a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes initial bandwidth parts associated with a second UE type when none of the one or more initial bandwidth parts included in the control message may be associated with the first UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes a default initial bandwidth part when none of the one or more initial bandwidth parts included in the control message may be associated with the first UE type and none of the one or more initial bandwidth parts included in the control message may be associated with the second UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the ranking prioritizes initial bandwidth parts associated with a third UE type when none of the one or more initial bandwidth parts included in the control message may be associated with the first UE type and none of the one or more initial bandwidth parts included in the control message may be associated with the second UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the second UE type may be a RedCap UE type and the third UE type may be an eMBB UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the first UE type may be associated with a first maximum bandwidth processing capability that may be lower than a second maximum bandwidth processing capability associated with eMBB UEs.

In some examples of the method, first network nodes, and non-transitory computer-readable medium described herein, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

Some examples of the method, first network nodes, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second control message indicating the ranking for the initial bandwidth part selection.

DETAILED DESCRIPTION

Some wireless communications systems may support multiple types of communication devices (e.g., user equipments (UEs)). For example, a wireless communications system may include higher capability UEs that support relatively low latency and relatively high data throughput communication, such as enhanced mobile broadband (eMBB) communications. Such UEs may be referred to as eMBB UEs. Additionally, or alternatively, the wireless communications system may include lower capability UEs, or reduced capability (RedCap) UEs, which may operate with one or more of a reduced transmit power, a reduced quantity of transmit or receive antennas, a reduced transmit or receive bandwidth, or a reduced computational complexity. As such, some RedCap UEs may support a reduced peak data throughput, reliability, bandwidth, or other characteristics or capabilities. In some examples, such as to support low-tier internet of things (IoT) functionality, the wireless communications system may also include eRedCap (enhanced RedCap, which may also be referred to as evolved RedCap) UEs with capabilities that may be reduced relative to RedCap UEs. Although eRedCap UEs are referred to throughout the present disclosure, it should be understood that the techniques described herein may also apply to other types of devices associated with a bandwidth processing capability that may be reduced relative to a bandwidth processing capability associated with eMBB UEs.

In some examples, eMBB UEs, RedCap UEs, and eRedCap UEs, among other UE types, may use a same set of time-frequency resources to transmit one or more messages as part of a random access procedure to establish a connection with a network entity. Such resources may be referred to as a random access occasion. For example, an eMBB UE, a RedCap UE, and an eRedCap UE may use a same random access occasion to transmit a random access request to the network entity. In such an example, each random access requests may include a preamble selected at the respective UE (e.g., the UE that transmitted the random access request). In response, the network entity may transmit a random access response to one or more of the UEs. The random access response may include, in its payload, an identifier of a UE that transmitted a random access request (e.g., the eMBB UE, the RedCap UE, or the eRedCap UE). For example, the random access response may include (e.g., indicate) an identifier corresponding to the preamble transmitted from the eRedCap UE. In some examples, however, a bandwidth supported at the eRedCap UE may be constrained, such that the eRedCap UE may be incapable of determining that a response was transmitted, or that the response may be intended for the eRedCap UE. That is, the eRedCap UE may be incapable of successfully decoding the random access response. In such an example, the eRedCap UE may retransmit the preamble to the network entity unnecessarily, which may lead to a reduced resource utilization within the wireless communications system.

Various aspects of the present disclosure generally relate to techniques for random access response schemes for eRedCap UEs, and more specifically, to schemes for transmitting random access responses to multiple UE types that support multiple (e.g., different) bandwidths. For example, a network entity may use a downlink control channel message (e.g., a grant) included in a random access response to indicate a UE type associated with the random access response. In some examples, the network entity may indicate the UE type using one or more bits (e.g., reserved bits) in a field of the downlink control channel message. For example, the UE may use one or more bits in a modulation and coding scheme (MCS) level field or a transport block scaling field (or both) to determine the UE type associated with the random access response.

Additionally, or alternatively, the network entity may use a radio network temporary identifier (RNTI) to indicate the UE type. For example, the network entity may determine an RNTI using a parameter that may be based on the UE type associated with the random access response message. In such an example, the network entity may use the determined RNTI to scramble cyclic redundancy check (CRC) bits included in the downlink control channel message. As such, the eRedCap UE and one or more other UEs may determine a UE type associated with the random access response based on the RNTI used to scramble the CRC bits. In some other examples, the network entity may configure the eRedCap UE with one or more initial bandwidth parts to be used for a random access procedure with the network entity. In such examples, each of the one or more initial bandwidth parts may be associated with a type (e.g., different types or a same type) of UE. In some examples, the eRedCap UE may select a bandwidth part to use for a random access procedure with the network entity (e.g., for transmitting a random access request) from the configured initial bandwidth parts. For example, the eRedCap UE may select a bandwidth part based on one or more rules, such as according to a selection hierarchy defined by the one or more rules.

Particular aspects of the subject matter described herein may be implemented to realize one or more potential advantages. For example, the techniques employed by the described communication devices may provide benefits and enhancements to the operation of the communication devices, including more efficient random access communications at eRedCap UEs. In some examples, operations performed by the described communication devices may also support reduced power consumption, increased throughput, and higher data rates, among other benefits.

Aspects of the disclosure are initially described in the context of wireless communications systems and process flows. Aspects of the disclosure are also illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to random access response schemes for eRedCap UEs.

FIG.1illustrates an example of a wireless communications system100that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The wireless communications system100may include one or more network entities105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, a network entity (which may alternatively be referred to as an entity, a node, a network node, or a wireless entity) may be, be similar to, include, or be included in (e.g., be a component of) a base station (e.g., any base station described herein, including a disaggregated base station), a UE (e.g., any UE described herein), a reduced capability (Redcap) device, an enhanced reduced capability (eRedCap) device, an ambient internet-of-things (IoT) device, an energy harvesting (EH)-capable device, a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and/or another processing entity configured to perform any of the techniques described herein. For example, a network entity may be a UE. As another example, a network entity may be a base station. As used herein, “network entity” may refer to an entity that is configured to operate in a network, such as the network entity105. For example, a “network entity” is not limited to an entity that is currently located in and/or currently operating in the network. Rather, a network entity may be any entity that is capable of communicating and/or operating in the network.

The adjectives “first,” “second,” “third,” and so on are used for contextual distinction between two or more of the modified noun in connection with a discussion and are not meant to be absolute modifiers that apply only to a certain respective entity throughout the entire document. For example, a network entity may be referred to as a “first network entity” in connection with one discussion and may be referred to as a “second network entity” in connection with another discussion, or vice versa. As an example, a first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different relative to these examples.

Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network entity. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network entity may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to transmit information to a second network entity. In this example and consistent with this disclosure, disclosure that the first network entity is configured to transmit information to the second network entity includes disclosure that the first network entity is configured to provide, send, output, communicate, or transmit information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that the first network entity is configured to transmit information to the second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network entity.

As shown, the network entity (e.g., network entity105) may include a processing system106. Similarly, the network entity (e.g., UE115) may include a processing system112. A processing system may include one or more components (or subcomponents), such as one or more components described herein. For example, a respective component of the one or more components may be, be similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to a second component and a third component. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system may generally be a system including one or more components that may perform one or more functions, such as any function or combination of functions described herein. For example, one or more components may receive input information (e.g., any information that is an input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information that is an output, such as a signal or any other information), one or more components may perform any function as described herein, or any combination thereof. As described herein, an “input” and “input information” may be used interchangeably. Similarly, as described herein, an “output” and “output information” may be used interchangeably. Any information generated by any component may be provided to one or more other systems or components of, for example, a network entity described herein. For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and/or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., that is coupled to the communication interface and/or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or a second communication interface). For example, a processing system may include at least one memory, at least one communication interface, and/or at least one processor, where the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

A processing system of a network entity described herein may interface with one or more other components of the network entity, may process information received from one or more other components (such as input information), or may output information to one or more other components. For example, a processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and/or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., that is coupled to the communication interface and/or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or a second communication interface). For example, a chip or modem of the network entity may include a processing system. The processing system may include a first communication interface to receive or obtain information, and a second communication interface to output, transmit, or provide information. In some examples, the first communication interface may be an interface configured to receive input information, and the information may be provided to the processing system. In some examples, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface may also obtain or receive input information, and the first communication interface may also output, transmit, or provide information.

A carrier may be associated with a particular bandwidth of the radio frequency spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., the network entities105, the UEs115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system100may include network entities105or UEs115that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating using portions (e.g., a sub-band, a bandwidth part) or all of a carrier bandwidth.

One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more bandwidth parts having the same or different numerologies. In some examples, a UE115may be configured with multiple bandwidth parts. In some examples, a single bandwidth part for a carrier may be active at a given time and communications for the UE115may be restricted to one or more active bandwidth parts.

The wireless communications system100may support schemes for transmitting random access responses to multiple UE types that support multiple (e.g., different) bandwidths. For example, a network entity105may use a downlink control channel message included in a random access response to indicate a UE type associated with the random access response. In some examples, a UE115may receive a random access response from the network entity105during a random access window associated with a random access request by the UE115. The UE115may determine that the random access response is associated with a first UE type. In such examples, the UE115may decode a transport block of the random access response based on the determination and the UE115being the first UE type (e.g., an eRedCap UE).

Additionally, or alternatively, the UE115may receive a control message indicating one or more initial bandwidth parts to be used for random access of the network entity105, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. In some examples, the UE115may determine that none of the one or more initial bandwidth parts included in the control message are associated with the first UE type (e.g., the first UE type corresponding to the UE115). In such examples, the UE115may select a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the network entity105. In some examples, the UE115may select the particular initial bandwidth part in accordance with a rule for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type. The UE115may transmit a random access request to the network entity105via the selected one of the one or more initial bandwidth parts. In some examples, transmitting the random access request using the selected one of the one or more initial bandwidth parts may lead to increased efficiency associated with random access within the wireless communications system100, among other possible benefits.

FIG.2illustrates an example of a wireless communications system200that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. In some examples, the wireless communications system200may implement or be implemented at one or more aspects of the wireless communications system100. For example, the wireless communications system200may include a UE215-aand a UE215-b, which may be examples of a UE115as described with reference toFIG.1. The wireless communications system200may also include a network entity205, which may be an example of one or more of the network entities105(e.g., a CU, a DU, an RU, a base station, an IAB node, or one or more other network nodes) as described with reference toFIG.1. The network entity205and the UEs215may communicate using a communication link220-aand a communication link220-b, which may be examples of a communication link125as described with reference toFIG.1. In the example ofFIG.2, the UEs215and the network entity205may communicate within a coverage area210, which may be an example of a coverage area110as described with reference toFIG.1. The wireless communications system200may include features for improved communications between the network entity205and the UEs215, among other possible benefits.

The wireless communications system200may include multiple UE types, such as smartphones (e.g., enhanced mobile broadband (eMBB) UEs), and one or more other vertical market UEs (e.g., ultra-reliable low latency communication (URLLC) UEs, V2X UEs), among other examples. Additionally, or alternatively, to achieve scalability and enable deployments in a more efficient and cost-effective manner, the wireless communications system200(e.g., an NR system) may include another UE type with reduced capabilities. For example, the wireless communications system200may include one or more RedCap UEs. In some examples, the wireless communications system200may support RedCap UEs by relaxing peak throughput, latency, and reliability constraints. In the example ofFIG.2, the UE215-amay be an example of an eMBB UE or a RedCap UE, which are examples of non-eRedCap UEs. In some examples, RedCap UEs may lead to a reduction on cost, complexity, and power consumption, among other possible benefits. Additionally, or alternatively, the wireless communications system200may support RedCap evolution, which may consider use of another UE type with further reduced capabilities to support one or more low-tier IoT use cases. Such UEs may be referred to as eRedCap UEs. In the example ofFIG.2, the UE215-bmay be an example of an eRedCap UE. For example, the wireless communications system200may support coexistence between non-eRedCap UEs, such as the UE215-a, and eRedCap UEs, such as the UE215-b.

In some examples, eRedCap UEs (e.g., NR eRedCap UEs) may be designed to reduce (e.g., minimize) UE complexity and reduce (e.g., further save) device costs. In such examples, UE bandwidth may also be reduced relative to other UE types (e.g., from an NR baseline). For example, to reduce costs and complexity relative to the UE215-a, the UE215-bmay support a reduced bandwidth or data rate (or both). That is, while an eMBB UE may support a bandwidth of about 100 MHz and a RedCap UE may support a bandwidth of about 20 MHz, an eRedCap UE may support a bandwidth of about 5 MHz for some communication channels. For example, the UE215-bmay support a baseband bandwidth reduction in which the UE215-bmay use about a 5 MHz baseband bandwidth for a PDSCH (e.g., for both unicast and broadcast) and a PUSCH. In some examples, the UE215-bmay support about a 20 MHz radio frequency bandwidth for one or more other channels, such as other uplink channels and other downlink channels. That is, eRedCap UEs may support about 20 MHz radio frequency bandwidth for baseband channels other than the PDSCH and the PUSCH.

In some examples, while eRedCap UEs and non-eRedCap UEs (e.g., RedCap UEs or eMBB UEs) may use multiple (e.g., different) preamble indices for a RACH procedure (e.g., a Msg1 based indication), the eRedCap UEs and the non-eRedCap UEs may share a same time-frequency location for transmission of a respective preamble. The time-frequency location used for transmission of a preamble may be referred to as a random access channel (RACH) occasion, a physical random access channel (PRACH) occasion, or a random access occasion. In some examples, the UE215-a(e.g., a non-eRedCap UE) and the UE215-b(e.g., an eRedCap UE) may each perform a random access procedure to establish a connection with the network entity205. In some examples, such as for a contention based random access procedure, the UE215-aand the UE215-bmay select a random access preamble (e.g., a preamble230-aand a preamble230-b, respectively) to transmit to the network entity205. In some examples, the UE215-aand the UE215-bmay include the respective preamble in random access request. The random access request may correspond to a first message (e.g., Msg1) of the random access procedure. For example, the UE215-aand the UE215-bmay use a random access request to transmit the preamble230-aand the preamble230-b, respectively, to the network entity205.

In the example ofFIG.2, the UE215-aand the UE215-bmay use a same PRACH occasion to transmit the preamble230-aand the preamble230-b, respectively, to the network entity205. In some examples, transmission of a random access preamble may be referred to as a PRACH transmission. In some examples, the network entity205may select the preamble230-aor the preamble230-bto establish a connection to the corresponding UE. That is, the network entity205may select the preamble230-ato establish a connection with the UE215-aor the preamble230-bto establish a connection with the UE215-b. Additionally, or alternatively, the network entity205may indicate the selected random access preamble to the UEs215. For example, the network entity205may transmit a random access response that indicates the selected preamble to the UEs215.

In response to receiving one or more random access requests, the network entity205may transmit a random access response, such as a random access response265-aand a random access response265-b. The random access response may include a random access response grant using a physical downlink control channel (PDCCH). That is, the random access response grant may include PDCCH signaling, such as downlink control information (DCI). In some examples, the random access response grant may be scheduled for UEs (e.g., all UEs) that share same PRACH occasion. For example, subsequent to a PRACH transmission during a PRACH occasion, the UE215-aand the UE215-bmay monitor for a random access response (e.g., DCI) during a duration (e.g., a random access response window, such as may be configured using a rar-WindowLength information element (IE) in a system information block (SIB) message). In some examples, the UE215-amay monitor the PDCCH during a window235-aand the UE215-bmay monitor the PDCCH during a window235-b. For example, the UE215-aand the UE215-bmay monitor the PDCCH for a random access response grant in which CRC bits included in the grant may be scrambled with a random access RNTI (RA-RNTI) corresponding to the PRACH transmission (e.g., the PRACH occasion). In some examples, the UE215-aand the UE215-bmay monitor the PDCCH for DCI of a format (e.g., a Format1_0) with CRC bits scrambled using the RA-RNTI corresponding to the PRACH occasion. That is, in response to receiving the preamble230-aor the preamble230-b, or both the preamble230-aand the preamble230-b, the network entity205may transmit a random access response including a grant240-aand another random access response including a grant240-busing the PDCCH. The grant240-aand the grant240-bmay be scrambled using an RA-RNTI associated with the PRACH occasion in which the preamble230-aand the preamble230-bwere transmitted from the UE215-aand the UE215-b, respectively. In such an example, if the UE215-aand the UE215-bsuccessfully detect (and decode) the grant240-aand the grant240-b, respectively, the UE215-aand the UE215-bmay decode a corresponding PDSCH message carrying random access response data. For example, the random access response265-amay include the grant240-aand a payload245-a(e.g., the PDSCH message carrying the random access response data, a transport block) corresponding to the grant240-a. In such an example, if the UE215-asuccessfully decodes the grant240-a, the UE215-amay determine to decode the payload245-a. Additionally, or alternatively, if the UE215-asuccessfully decodes the payload245-a, the UE215-amay proceed to transmit a third message (e.g., Msg3) of the random access procedure.

In some examples, such as for NR systems, the RA-RNTI may be determined (e.g., calculated) in accordance with the following Equation 1:

in which s_id may correspond to an index of a relatively first OFDM symbol of the PRACH occasion (e.g., 0≤s_id<14). Additionally, or alternatively, t_id may correspond to an index of a relatively first slot of the PRACH occasion in a system frame (e.g., 0≤t_id<80). In some examples, a subcarrier spacing to determine t_id may be based on a value of a parameter (μ), which may be configured at the network entity205and the UEs215. In some examples, f_id may correspond to an index of the PRACH occasion in a frequency domain (0≤f_id<8) and ul_carrier_id may correspond to an uplink carrier used at the UE215-aand the UE215-bfor the PRACH transmission (e.g., ul_carrier_id may correspond to a value of 0 for a normal uplink (NUL) carrier and 1 for a supplementary uplink (SUL) carrier). In such examples, the RA-RNTI may be determined (e.g., calculated) irrespective of a preamble identifier (ID) indicated using the random access response. That is, the RA-RNTI calculation may depend on time-frequency location of the PRACH resource (e.g., the PRACH resource used for the PRACH transmission, the PRACH occasion), but may not depend on a preamble ID of a PRACH sequence (e.g., a preamble indicated using the random access response). In some examples, a preamble ID may include a preamble index, such as may be indicated using an RRC parameter (e.g., an ra-PreambleIndex field of an IE transmitted using RRC signaling). In such examples, UEs that transmit a random access request (e.g., a PRACH, a preamble) at same time-frequency location (e.g., using a same PRACH occasion), may be able to decode a same random access response grant (e.g., an RA-RNTI grant). For example, due to the UE215-aand the UE215-busing a same PRACH occasion to transmit the preamble230-aand the preamble230-b, respectively, the UE215-aand the UE215-bmay be able to decode a random access response grant that is scrambled using a same RA-RNTI (e.g., an RA-RNTI calculated based on the PRACH occasion). In some examples, the ability to decode a random access response grant may be based on whether the UEs have sufficient coverage to receive the random access response grant. That is, the UE215-aand the UE215-bmay be able to decode random access response grants (e.g., one or more grants240) if the UEs215have sufficient coverage to receive the random access response grants.

In some examples, if the UEs215fail to successfully receive a payload included in a random access response grant, the UEs215may be configured to retransmit a preamble. For example, if the UE215-aand the UE215-breceive and successfully decode the grant240-aand the grant240-b, the UE215-aand the UE215-bmay attempt to decode the corresponding payload (e.g., the payload245-aand the payload245-b, respectively). In some examples, if the UE215-aand the UE215-bfail to decode the corresponding payload within the window235-aand the window235-b, respectively, the UE215-aand the UE215-bmay determine to retransmit the preambles230. For example, the UE215-amay determine to retransmit the preamble230-aand the UE215-bmay determine to retransmit the preamble230-b. That is, if a UE fails to successfully receive (and decode) a payload (e.g., a transport block in a corresponding PDSCH) within a random access response window, one or more relatively higher layers (e.g., of a protocol stack associated with the UE) may indicate to a physical layer (e.g., of the protocol stack associated with the UE) to transmit (or retransmit) a PRACH. In some examples, if requested by the relatively higher layers, the UE may transmit (or retransmit) a PRACH during some duration (e.g., no later than about NT,1+0.75 ms, in which NT,1may correspond to a time duration of symbols corresponding to a PDSCH processing time for the UE) subsequent to a relatively last symbol of the window, or a relatively last symbol of the PDSCH reception. That is, the UE may retransmit the PRACH prior to an end of the window if the UE detects a random access grant (e.g., a DCI scrambled via an RA-RNTI) but fails to decode the corresponding payload (e.g., the random access response payload, the PDSCH message carrying the random access response data).

Additionally, or alternatively, a UE may be configured to retransmit a preamble (e.g., a PRACH), if a random access response payload (e.g., the PDSCH message carrying the random access response data, the transport block) fails to include an ID corresponding to the preamble transmitted from the UE (e.g., a preamble ID selected at the UE). For example, the UE215-bmay determine that the payload245-bfails to include an ID corresponding to the preamble230-b. In some examples, however, a bandwidth260-aused at the network entity205to transmit the payload245-bmay exceed a bandwidth260-bsupported at the UE215-b. For example, the network entity205may transmit the payload245-b, which may include an ID corresponding to the preamble230-b, using the bandwidth260-a(e.g., a bandwidth of about 20 MHz) and the UE215-b(e.g., an eRedCap UE) may support a bandwidth260-b(e.g., a bandwidth of about 5 MHz). For example, a bandwidth of a shared channel255capable of being monitored at the UE215-bmay correspond to a bandwidth260-b. In such an example, the UE215-bmay be incapable of successfully decoding the payload245-band may determine to retransmit the preamble230-birrespective of the payload245-bincluding the ID corresponding to the preamble230-b. Additionally, or alternatively, the UE215-a(e.g., a non-eRedCap UE, such as an eMBB UE or a RedCap UE) may support a bandwidth of about 20 MHz. As such, the UE215-amay successfully decode a payload transmitted from the network entity using the bandwidth260-a. That is, the UE215-amay support the bandwidth260-aand the UE215-bmay support the bandwidth260-b. In such examples, the network entity205may be incapable of transmitting random access responses using bandwidths supported at the UE215-aand the UE215-b. For example, the network entity205may be incapable of determining how to send a random access response to two sets of UEs that may support multiple (e.g., different) baseband bandwidths. Although the example ofFIG.2illustrates the grant240-band the payload245-bspanning the bandwidth260-a, it is to be understood that the grant240-band the payload245-bmay span multiple different bandwidths, including the bandwidth260-b.

In some examples, if both eRedCap UEs and non-eRedCap UEs (e.g., RedCap UEs or eMBB UEs) transmit a PRACH using same PRACH occasion, the eRedCap UEs and the non-eRedCap UEs may both be able to decode the corresponding random access response grant (e.g., if the eRedCap and non-eRedCap UEs have sufficient coverage). For example, the UE215-aand the UE215-bmay be capable of decoding the grant240-aand the grant240-b, respectively, due to the preamble230-aand the preamble230-bbeing transmitted using a same PRACH occasion. In such an example, the non-eRedCap UEs may be capable of decoding corresponding random access response payload. However, due to a constrained shared channel bandwidth (e.g., due to eRedCap UEs supporting a PDSCH bandwidth of about 5 MHz), some eRedCap UEs may be incapable of decoding the corresponding random access response payload. For example, a set of eRedCap UEs that have relatively good coverage may be incapable of decoding the random access response payload. In some examples, if eRedCap UEs fail to decode the random access response payload, the eRedCap UEs may retransmit the PRACH, irrespective of the random access response payload including an ID corresponding to a preamble selected at the UEs. For example, the UE215-amay be capable of decoding the payload245-a, but the UE215-bmay be incapable of decoding the payload245-b. In such an example, the UE215-bmay retransmit the preamble230-birrespective of whether the payload245-bincludes an ID corresponding the preamble230-b, which may lead to increased random access (e.g., RACH) latency within the wireless communications system200.

In some examples, the UE215-bmay be capable of indicating, to the network entity205, that the UE215-bsupports reduced capabilities (e.g., that the UE215-bmay be an eRedCap UE). For example, the UE215-band the network entity205may support one or more mechanisms for relatively early indication, from the UE215-b, that the UE215-bmay be an eRedCap UE or one or more other UE types that may have reduced capabilities. In some examples, a relatively early indication of eRedCap UEs (e.g., operating within the wireless communications system200) may be enabled through one or more schemes. For example, the UE215-bmay use a message transmitted as part of a random access procedure (e.g., Msg1) to indicate that the UE215-bmay be an eRedCap UE. That is, the UE215-bmay support a Msg1-based early indication scheme. In some examples, the UE215-bmay use an initial bandwidth part to transmit the message (e.g., the Msg1). In such an example, in response to receiving the message from the UE215-b, the network entity205may assign another initial bandwidth part (e.g., a separate initial bandwidth part) for the UE215-b. For example, a quantity of PRACH occasions capable of being included in an initial bandwidth part may be constrained and, as such, using different PRACH occasions for multiple (e.g., different) UE types might be relatively costly. Thus, in some examples, the network entity205may assign different initial bandwidth parts to non-eRedCap UEs (e.g., the UE215-a) and eRedCap UEs (e.g., the UE215-b). In some other examples, a quantity of PRACH occasions capable of being included in an initial bandwidth part may be suitable for multiple types of UEs. In such examples, the network entity205may assign an initial bandwidth part that may be shared between the non-eRedCap UEs (e.g., the UE215-a) and eRedCap UEs (e.g., the UE215-b). For example, in response to receiving an indication that the UE215-bmay be an eRedCap UE, the network entity205may assign an initial bandwidth part to the UE215-bthat may be shared with the UE215-a. In some examples, the network entity205may assign multiple (e.g., separate) time-frequency locations for PRACH resources used at the UE215-aand the UE215-b. In some other examples, the network entity205may assign a same time-frequency location for a PRACH resource to be used at the UE215-aand the UE215-b. In such examples, the network entity205may configure the UE215-aand the UE215-bwith multiple (e.g., different) set of preamble indices. Additionally, or alternatively, the UE215-bmay use another message transmitted as part of a random access procedure (e.g., Msg3) to indicate that the UE215-bmay be an eRedCap UE. For example, the UE215-bmay support a Msg3-based early indication scheme.

In some examples, the wireless communications system200may support one or more random access response schemes for UEs with constrained bandwidths, such as eRedCap UEs. For example, the network entity205may use a random access response grant to indicate a UE type associated with the random access response grant and the corresponding payload. As illustrated in the example ofFIG.2, the UE215-aand the UE215-bmay receive one or multiple random access responses (e.g., each including a respective grant240and a respective payload245) from the network entity205during a random access window that may be associated with a random access request. For example, the UE215-aand the UE215-bmay receive one or multiple random access responses from the network entity205during the windows235-aand the window235-b, respectively, that may be associated with the preambles230-aand the preamble230-b. In response to receiving a random access response from the network entity205, the UE215-aor and the UE215-bmay determine that the random access response is associated with a UE type and may decode a transport block of the random access response (e.g., the payload245) based on the indicated UE type. For example, the network entity205may include a UE type indication250in a grant240-b. The UE type indication250may indicate, to the UE215-b, that the grant240-band the corresponding payload (e.g., the payload245-b) may be associated with eRedCap UEs. For example, the UE type indication250may indicate that the payload245-bmay be transmitted using a reduced bandwidth, such as bandwidth that may be supported at the UE215-b(or one or more other eRedCap UEs). In such an example, the UE215-bmay determine to decode the payload245-bbased on the UE type indication250indicating a UE type corresponding to the UE215-b.

In some examples, the network entity205may use one or more fields in reserved bits of a random access response grant to indicate the UE type. For example, the network entity205may be capable of indicating whether the random access response grant (e.g., including the UE type indication) may be applicable for eRedCap UEs using these fields. That is, the network entity205may use a field included in the random access response grant to indicate whether the random access response grant may be intended for eRedCap UEs or one or more other UE types. As illustrated in the example ofFIG.2, the network entity205may use one or more reserved bits included in the grant240-b(e.g., DCI) to signal the UE type indication250to the UE215-b. In some examples, in response to receiving the UE type indication250, the UE215-b(e.g., an eRedCap UE) may attempt to decode a random access response payload corresponding to the random access response grant. For example, the network entity205may use reserved bits included in the grant240-bto indicate that the payload245-bis intended for eRedCap UEs (e.g., is transmitted using a bandwidth suitable for eRedCap UEs). In such an example, the UE215-bmay attempt to decode the payload245-bin response to determining (e.g., based on decoding the grant240-b) that the payload245-bis intended for eRedCap UEs. In some other examples, the UE215-bmay determine (e.g., based on decoding the grant240-b) that the payload245-bmay be intended for another UE type. In such examples, the UE215-bmay refrain from decoding (e.g., reading) the payload245-band monitor the PDSCH (e.g., continue to monitor the PDSCH, wait) within the window235-bfor one or more other random access response grants. That is, in such examples, an eRedCap UE may wait to receive another random access response grant that may be intended for the eRedCap UE within a random access response window. For example, the UE215-bmay monitor for (and receive) a grant240-c. In such an example, the grant240-cmay include one or more reserved bits that indicate that the payload245-cis intended for eRedCap UEs. In such an example, the UE215-bmay attempt to decode (e.g., read) the payload245-c.

In some examples, to indicate a UE type to eRedCap UEs, the network entity205may send one or multiple random access response grants. For example, the network entity205may send a random access response grant twice or more than twice. In such an example, a first random access response grant may be intended for non-eRedCap UEs (e.g., RedCap UEs or eMBB UEs), such as the UE215-a, and a second random access response grant may be intended for eRedCap UEs, such as the UE215-b. For example, the network entity may transmit the grant240-aand a grant240-b, which may be intended for the UE215-aand the UE215-b, respectively. In such an example, the grant240-bmay include the UE type indication250.

For example, the grant240-bmay be an example of a downlink control channel message that includes UE type information indicative of one or more UE types with which the downlink control channel message (e.g., the grant240-b) may be associated. That is, the network entity205may use the UE type indication250to indicate one or more UE types, such as eRedCap UEs or one or more other UE types, such as one or more future UE types. In some examples, the grant240-bmay include one or more bits (e.g., in a field) that indicate one or more UE types for which the grant240-bis associated. That is, the UE type information (e.g., the UE type indication250) may be included in one or more bits in a field included in the grant240-band each bit of the one or more bits or multiple bits of the one or more bits may correspond to a respective UE type. Additionally, or alternatively, each bit of the one or more bits or multiple bits of the one or more bits may correspond to a respective group of UE types. In some examples, the network entity205may use multiple reserved bits included in the grant240-b(e.g., a random access response grant, a downlink control channel message) to indicate whether the corresponding random access response payload is intended for one or multiple UE types. In some examples, a same bit may be reserved for multiple different UE types. Additionally, or alternatively, the network entity205may configure the UEs215with mapping information associated with the reserved bits to indicate different UE types that may be configured via the network entity205. That is, the mapping information may be used at the UEs215to map each bit (or multiple bits) included in the field to the respective UE type. Additionally, or alternatively, the mapping information may be used at the UEs215to map each bit (or multiple bits) included in the field to the respective group of UE types. In some examples, the network entity205may transmit information associated with the mapping through system information or a handover command.

In some examples, a UE may receive a random access response grant unintended for the UE prior to receiving a random access response grant intended for the UE. For example, the network entity may transmit a first random access response grant for non-eRedCap UEs (e.g., RedCap or eMBB UEs) and a second random access response grant for eRedCap UEs. In such an example, if an eRedCap UE receives the first random access response grant (e.g., prior to the second random access response grant), the eRedCap UE may refrain from decoding a payload corresponding to the first random access response grant. For example, based on decoding the first random access response grant, the eRedCap UE may determine that the first random access response grant includes a UE type indication that indicates a UE type other than eRedCap UEs (or fails to include a UE type indication). Additionally, or alternatively, if a non-eRedCap UE receives the second random access response grant prior to the first random access response grant, the non-eRedCap UE may attempt to decode the corresponding payload. For example, the non-eRedCap UE may be incapable of decoding the bits included in the second random access response grant that indicate that the corresponding payload is intended for eRedCap UEs.

As illustrated in the example ofFIG.2, the UE215-amay fail to receive (or fail to successfully decode, such as due to link coverage) a grant that may be intended for non-eRedCap UEs. Additionally, or alternatively, the UE215-amay receive a grant intended for eRedCap UEs prior to receiving a grant intended for a non-eRedCap (e.g., a RedCap or eMBB) UEs. For example, the UE215-amay receive the grant240-aprior to receiving a grant240-d(e.g., associated with a payload245-d). In such an example, the grant240-amay be intended for eRedCap UEs and the grant240-dmay be intended for non-eRedCap UEs. That is, the grant240-amay include one or more reserved bits that indicate that the corresponding payload (e.g., the payload245-a) is intended for eRedCap UEs (or another UE type different from a RedCap UE or an eMBB UE). In such an example, the UE215-amay be incapable of decoding the one or more reserved bits and may therefore be unaware that the payload245-ais intended for eRedCap UEs. Accordingly, the UE215-amay attempt to decode the payload245-a. In some examples, based on decoding the payload245-a, the UE215-amay determine that the payload245-afails to include an identifier associated with the preamble230-aand may determine to re-transmit the preamble230-a(e.g., unnecessarily) prior to receiving the grant240-d(e.g., the grant intended for non-eRedCap UEs).

In some examples, to avoid a case in which the non-eRedCap UE (e.g., a RedCap UE or an eMBB UE) may read a random access response grant (or the corresponding payload) intended for eRedCap UEs, the network entity205may include an indication for the eRedCap UE and the non-eRedCap UE. For example, the network entity205may use one or more fields of multiple fields included in the random access response grant to indicate that the random access response grant is intended for eRedCap UEs and that the non-eRedCap UE is to refrain from decoding the corresponding payload. In some examples, the network entity205may use an MCS field, a transport block scaling field, or both. For example, the network entity205may use a first MCS level field (e.g., a field decodable at the non-eRedCap UE) to indicate that the corresponding payload is intended for eRedCap UEs and that non-eRedCap UEs may refrain from decoding the corresponding payload. In some examples, to indicate for the non-eRedCap UE to refrain from decoding the corresponding payload, the first MCS level field may indicate “Reserved.” For example, the non-eRedCap UE may determine that an MCS for the corresponding payload (e.g., a transport block) is reserved based on the first MCS level field included in the random access response grant indicating “Reserved.” In such examples, the non-eRedCap UE may determine that the random access response grant is invalid and may refrain from decoding (e.g., may ignore) the corresponding payload. Additionally, or alternatively, the network entity205may use a second MCS level field included in the grant intended for the eRedCap UEs to indicate an MCS level to be used at the eRedCap UEs to decode the corresponding payload. In some examples, the network entity205may use reserved bits included in the random access response grant (e.g., a PDCCH message, such as DCI) to include the second MCS level field (e.g., for the eRedCap UEs).

In the example ofFIG.2, a first MCS level field included in the grant240-amay indicate that the random access response including the grant240-aand the payload245-ais associated with eRedCap UEs. Additionally, or alternatively, a second MCS level field included in the grant240-amay indicate an MCS level for the payload245-a. In such an example, the UE215-amay refrain from decoding the payload245-a(e.g., may determine that the grant240-ais invalid). Additionally, or alternatively, a first MCS level field included in the grant240-bmay indicate that the random access response including the grant240-band the payload245-bis associated with eRedCap UEs. Additionally, or alternatively, a second MCS level field included in the grant240-bmay indicate an MCS level for the payload245-b. In such an example, the UE215-bmay decode the payload245-busing the indicated MCS level. In some examples, the first MCS level field may correspond to the UE type indication250.

Additionally, or alternatively, the network entity205may use a first transport block scaling field (e.g., a field decodable at the non-eRedCap UE) to indicate that the corresponding payload is intended for eRedCap UEs and that the non-eRedCap UE may refrain from decoding the corresponding payload. In some examples, to indicate for the non-eRedCap UE to refrain from decoding the corresponding payload, one or more bits associated with the second transport block scaling field may be set to a value, such as “11.” For example, the non-eRedCap UE may determine that an MCS for the corresponding payload (e.g., a transport block) is reserved based on the second transport block scaling field included in the random access response grant indicating “11,” which may correspond to reserved. In such examples, the non-eRedCap UE may determine that the transport block scaling field is invalid and may refrain from decoding (e.g., may ignore) the corresponding payload. Additionally, or alternatively, the network entity205may use a second transport block scaling field included in the grant intended for eRedCap UEs to indicate, to the eRedCap UE, a transport block scaling for the corresponding payload. In some examples, the network entity205may use reserved bits included in the random access response grant (e.g., a PDCCH, such as DCI) to include the second transport block scaling field (e.g., for the eRedCap UE).

As illustrated in the example ofFIG.2, a first transport block scaling field included in the grant240-amay indicate that the random access response including the grant240-aand the payload245-ais associated with eRedCap UEs (e.g., that the transport block scaling for the payload245-ais reserved). In such an example, the UE215-amay refrain from decoding the payload245-a(e.g., may determine that the grant240-ais invalid). Additionally, or alternatively, a first transport block scaling field included in the grant240-bmay indicate that the random access response including the grant240-band the payload245-bis associated with eRedCap UEs. Additionally, or alternatively, a second transport block scaling field included in the grant240-bmay indicate a transport block scaling for the payload245-b. In such an example, the UE215-bmay decode the payload245-busing the indicated transport block scaling. In some examples, the first transport block scaling field may correspond to the UE type indication250.

In some other examples, the network entity205may indicate a UE type associated with a random access response grant using an RA-RNTI. For example, an RA-RNTI calculation may incorporate a UE type. In some examples, incorporating a UE type into an RA-RNTI calculation may enable the network entity205to transmit multiple (e.g., different) random access responses among different UE types (e.g., relatively smoothly). In some examples, the network entity205(e.g., and the UEs215) may determine (e.g., calculate) the RA-RNTI using one or more parameters. For example, the RA-RNTI may be determined in accordance with (e.g., may take the form of) the following Equation 2:

in which the parameter UE_type may correspond to a value of 0 for non-RedCap UEs (e.g., eMBB UEs, RedCap UEs, or one or more other UE types). Additionally, or alternatively, the parameter UE_type may correspond to a value of 1 for eRedCap UEs. In some examples, the parameter UE_type may correspond to another value (e.g., a value other than 0 or 1) for another UE type. That is, multiple values may be used to indicate multiple (e.g., different) UE types. As illustrated in the example ofFIG.2, the network entity205may use an RA-RNTI determined with the parameter UE_type set to a value of 1 to scramble CRC bits included in the grant240-b. In such an example, the UE215-bmay determine that the grant240-bincludes CRC bits that are scrambled by an RA-RNTI that is associated with eRedCap UEs. For example, the UE215-bmay determine (e.g., calculate) a CRC value for the grant240-bbased on a UE_type parameter (e.g., an index value, an identifier) representative of eRedCap UEs (e.g., with a value of 1). In such an example, the UE215-bmay determine to decode the payload245-b.

In some other examples, the wireless communications system200may support a random access response scheme in which the network entity205may configure multiple (e.g., different) time-frequency resources among multiple (e.g., different) UE types. For example, the network entity205may configure multiple (e.g., different) PRACH occasions among eRedCap UEs (e.g., the UE215-b) and non-eRedCap UEs (e.g., the UE215-a). In such an example, an RA-RNTI for eRedCap UEs and non-eRedCap UEs may be (e.g., remain) different, for example based on one or more calculations (e.g., in accordance with Equation 1). Additionally, or alternatively, in such examples, the network entity205may refrain from sending a random access response (e.g., data associated with the random access response) for eRedCap UEs and non-eRedCap UEs in a same payload (e.g., a random access response PDSCH payload). In some examples, a quantity of PRACH occasions capable of being included in each initial bandwidth part may be constrained and, as such, using different PRACH occasions for multiple (e.g., different) UE types might be relatively costly.

In some examples, the network entity205may configure different initial bandwidth parts for eRedCap and non-eRedCap UEs. As illustrated in the example ofFIG.2, the UE215-bmay receive a control message270from the network entity205that may indicate one or more initial bandwidth parts to be used for a random access procedure with the network entity205. In such an example, each of the one or more initial bandwidth parts may be associated with a type (e.g., different types) of UE. In some examples, the UE215-bmay determine to use an initial bandwidth part associated with eRedCap UEs for a random access procedure with the network entity205(e.g., to transmit the preamble230-bor one or more other messages). Additionally, or alternatively, the UE215-bmay determine that none of the initial bandwidth parts included in the control message270are associated with eRedCap UEs. In such an example, the UE215-b(e.g., an eRedCap UE) may select one or more of the initial bandwidth parts included in the control message270to use for the random access procedure with the network entity205. For example, the UE215-bmay select a single initial bandwidth part or multiple initial bandwidth parts. In such an example, the UE215-bmay transmit a random access request (e.g., the preamble230-b) to the network entity205via the selected initial bandwidth part. That is, the UE215-bmay transmit the random access request (e.g., the preamble230-b) to the network entity205using a single selected initial bandwidth part or multiple selected bandwidth parts.

In some examples, the UE215-bmay select an initial bandwidth part included in the control message270based on one or more rules. For example, the UE215-bmay receive an indication from the network entity205of one or more rules for initial bandwidth part selection. The UE215-bmay receive the indication from the network entity205if none of the initial bandwidth parts included in the control message270are associated with eRedCap UEs. Additionally, or alternatively, the UE215-bmay be otherwise configured (e.g., preconfigured) with one or more rules for initial bandwidth part selection. In some examples, the one or more rules may include conditional expressions, such as if/then statement, or other logical expressions or statements, among other examples of rules that may be used for a selection. For example, a rule may define a selection hierarchy. That is, the UE215-bmay select an initial bandwidth part among the one or more initial bandwidth parts in accordance with a selection hierarchy. In some examples, the hierarchy may prioritize initial bandwidth parts based on a likeness between eRedCap UEs and other UE types that may be associated with the configured initial bandwidth parts. For example, the hierarchy may prioritize an initial bandwidth part associated with RedCap UEs over other initial bandwidth parts that may be associated with eMBB UEs. In such an example, if an initial bandwidth part (e.g., a separate initial bandwidth part) for eRedCap UEs is not configured, the UE215-bmay select a bandwidth part configured for RedCap UEs. That is, if a RedCap initial bandwidth part is configured (e.g., using the control message270), the UE215-b(e.g., an eRedCap UE) may use the RedCap initial bandwidth part as the initial bandwidth part for eRedCap UEs. In some examples, a RedCap initial bandwidth part may not be configured. In such examples, the UE215-bmay select an initial bandwidth part associated with another UE type or the UE215-bmay select a default initial bandwidth part (e.g., an NR bandwidth part). For example, if a RedCap initial bandwidth part is not configured, the UE215-bmay use a default initial bandwidth part as the initial bandwidth part for eRedCap UEs. In some examples, selecting an initial bandwidth part in accordance with one or more rules may enable increased flexibility (e.g., and increased resource usage) at the network entity205, among other possible benefits.

FIG.3illustrates an example of a process flow300that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. In some examples, the process flow300may implement one or more aspects of wireless communications system100and the wireless communications system200. For example, the process flow300may include example operations associated a network entity305, a UE315-a, and a UE315-b, which may be examples of the corresponding devices described with reference toFIGS.1and2. The operations performed by the network entity305and the UEs315may support improvements to communications between the UEs315and the network entity305, among other benefits. In the following description of the process flow300, the operations between the UEs315and the network entity305may occur in a different order than the example order shown. Additionally, or alternatively, the operations performed by the UEs315and the network entity305may be performed in different orders or at different times. Some operations may also be omitted.

In some examples, multiple UE types may use a same set of time-frequency resources (e.g., a same random access occasion) to transmit a random access request to a network entity as part of a random access procedure for establishing a connection with the network entity. For example, at320, the UE315-bmay transmit a random access request (e.g., including a random access preamble) to the network entity305using a random access occasion. In such an example, at325, the UE315-amay transmit another random access request to the network entity305using the same random access occasion. In response, the network entity305may transmit a random access response to the UE315-aand the UE315-b. In the example ofFIG.3, the UE315-amay be an example of a non-eRedCap UE, such as a RedCap UE or an eMBB UE. Additionally, or alternatively, the UE315-bmay be an example of an eRedCap UE. That is, the UE315-bmay be associated with an eRedCap UE type, which may correspond to reduced capabilities with respect to a RedCap UE type and an eMBB UE type (e.g., a UE type associated with the UE315-a).

At330, the network entity305may transmit the random access response to the UE315-aand the UE315-bduring a random access window associated with the random access requests (e.g., transmitted at320and325). The random access response may be an example of a random access response as described throughout the present disclosure, including with reference toFIG.2. For example, the random access response may include a downlink control channel message (e.g., a grant) that includes UE type information indicative of one or more UE types with which the downlink control channel message may be associated. For example, the downlink control channel message may include one or more bits (e.g., in a field) that indicate one or more UE types for which the downlink control channel message is associated. That is, the UE type information may be included in one or more bits in a field included in the downlink control channel message. In some examples, the one or more bits may indicate that the random access response is associated with a first UE type, such as eRedCap UEs. That is, the one or more UE types may include the first UE type. Additionally, or alternatively, the first UE type may be associated with a first bandwidth processing capability (e.g., a first maximum processing capability or otherwise suitable processing capability) that may be reduced relative to (e.g., lower than) a second bandwidth processing capability (e.g., a second maximum processing capability or otherwise suitable processing capability) associated with eMBB UEs. In some examples, first bandwidth processing capability may pertain to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

In some examples, the UE type information may include respective UE type information for each respective UE type of the one or more UE types. In such examples, the UE315-b, may receive mapping information that maps each respective UE type information of the UE type information to a respective UE type of the one or more UE types. Additionally, or alternatively, one or more of the respective UE type information of the UE type information may correspond to a group of different UE types.

At335, in response to receiving the random access response from the network entity305, the UE315-bmay determine that the random access response is associated with the first UE type. For example, the UE315-bmay determine that the random access response is associated with the first UE type based on the mapping information. In some examples, the mapping information may include a mapping between the one or more UE types and different sets of one or more bits included in the field of the random access response. That is, the mapping may be an example of a mapping as described throughout the present disclosure, including with reference toFIG.2. For example, the mapping may include a set of the one or more bits in the field that is representative of a group of different UE types. In some examples, the UE315-bmay receive the mapping information from the network entity305, such as in a system information message or a handover command.

Additionally, or alternatively, the UE315-bmay determine that the random access response is associated with the first UE type based on an RNTI, such as an RA-RNTI, used to scramble CRC bits included in the random access response. For example, the UE315-bmay determine that the random access response includes a CRC value that is scrambled by an RA-RNTI that is associated with the first UE type. In such an example, the UE315-bmay calculate the RA-RNTI value based on an index representative of the first UE type, in accordance with Equation 2. That is, the RA-RNTI may be based on an index value associated with the first UE type. In some examples, the index may be one or multiple indices representative of multiple (e.g., different) UE types. For example, the index value may be one of multiple index values indicated to (or otherwise configured at) the UE315-b. In such an example, each respective index value may be associated with a respective UE type (e.g., of the multiple UE types including the first UE type).

At340, the UE315-bmay decode a transport block of the random access response based on the first UE type. For example, the UE315-bmay decode the transport block based on a determination that the UE315-bis the first UE type (or of another UE type) and based on the random access response being associated with the first UE type. That is, the UE315-bmay decode the transport block based on the UE315-bbeing an eRedCap UE and the random access response being associated with eRedCap UEs.

FIG.4illustrates an example of a process flow400that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. In some examples, the process flow400may implement one or more aspects of wireless communications system100, the wireless communications system200, and the process flow300. For example, the process flow400may include example operations associated a network entity405and a UE415, which may be examples of the corresponding devices described with reference toFIGS.1through3. The operations performed by the network entity405and the UE415may support improvements to communications between the UE415and the network entity405, among other benefits. In the following description of the process flow400, the operations between the UE415and the network entity405may occur in a different order than the example order shown. Additionally, or alternatively, the operations performed by the UE415and the network entity405may be performed in different orders or at different times. Some operations may also be omitted. In some other examples, the network entity405may configure the UE415with multiple (e.g., different) time-frequency resources that may be associated with multiple (e.g., different) UE types.

At420, the UE415may receive a control message from the network entity405. The control message may be an example of a control message as described throughout the present disclosure, including with reference toFIG.2. For example, the control message may indicate one or more initial bandwidth parts to be used for random access of the network entity405. In some examples, each of the one or more initial bandwidth parts may be associated with a respective one or more UE types. For example, the one or more initial bandwidth parts may be associated with multiple (e.g., different) UE types.

At425, the UE415may determine that none of the initial bandwidth parts included in the control message received at420are associated with a first UE type. In the example ofFIG.4, the first UE type corresponds to an eRedCap UE type. For example, the UE415may determine that none of the initial bandwidth parts are associated with eRedCap UEs. That is, the UE415may determine that eRedCap UEs are unassociated with the initial bandwidth parts included in (or indicated by) the control message.

At430, the UE415may select one of the initial bandwidth parts (e.g., a particular initial bandwidth part, a single initial bandwidth part) for use in a random access procedure with the network entity405. In some examples, the UE415may select the particular initial bandwidth part from the one or more initial bandwidth parts included in the control message in accordance with a rule for initial bandwidth part selection. For example, the UE415may select the particular initial bandwidth part according to a rule for bandwidth part selection, for example if none of the one or more initial bandwidth parts included in the control message are associated with the first UE type (e.g., eRedCap UEs). The rule may be an example of one or more rules as described throughout the present disclosure, including with reference toFIG.2. For example, the rule may indicate for the UE415to select the particular initial bandwidth part among the one or more initial bandwidth parts in accordance with a hierarchy. That is, the rule may define a selection hierarchy. In some examples, the selection hierarchy may prioritize (e.g., rank) initial bandwidth parts associated with RedCap UEs over initial bandwidth parts associated with other UE types, such as eMBB UEs. In some examples, the UE415may select multiple initial bandwidth parts.

At435, the UE415may transmit a random access request to the network entity405via the selected initial bandwidth part (or via multiple selected initial bandwidth parts) included in the control message. The random access request many be an example of a random access request as described throughout the present disclosure, including with reference toFIG.2. For example, the random access request may be transmitted from the UE415as part of a random access procedure with the network entity405.

The transmitter515may provide a means for transmitting signals generated by other components of the device505. For example, the transmitter515may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to random access response schemes for eRedCap UEs). In some examples, the transmitter515may be co-located with a receiver510in a transceiver module. The transmitter515may utilize a single antenna or a set of multiple antennas.

The communications manager520, the receiver510, the transmitter515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager520may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver510, the transmitter515, or both. For example, the communications manager520may receive information from the receiver510, send information to the transmitter515, or be integrated in combination with the receiver510, the transmitter515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager520may support wireless communication at a first network node (e.g., the device505) in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for receiving a random access response from a second network node during a random access window associated with a random access request by the first network node. The communications manager520may be configured as or otherwise support a means for determining that the random access response is associated with a first UE type. The communications manager520may be configured as or otherwise support a means for decoding a transport block of the random access response based on the determination and the first network node being the first UE type.

Additionally, or alternatively, the communications manager520may support wireless communication at a first network node (e.g., the device505) in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types. The communications manager520may be configured as or otherwise support a means for determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The communications manager520may be configured as or otherwise support a means for selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources. The communications manager520may be configured as or otherwise support a means for transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

Additionally, or alternatively, the communications manager520may support wireless communication at a first network node (e.g., the device505) in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. The communications manager520may be configured as or otherwise support a means for determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The communications manager520may be configured as or otherwise support a means for selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts. The communications manager520may be configured as or otherwise support a means for transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

By including or configuring the communications manager520in accordance with examples as described herein, the device505(e.g., a processor controlling or otherwise coupled with the receiver510, the transmitter515, the communications manager520, or a combination thereof) may support techniques for more efficient utilization of communication resources.

The device605, or various components thereof, may be an example of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager620may include a window component625, a UE type component630, a random access response component635, a control message component640, a selection component645, a random access request component650, or any combination thereof. The communications manager620may be an example of aspects of a communications manager520as described herein. In some examples, the communications manager620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager620may support wireless communication at a first network node (e.g., the device605) in accordance with examples as disclosed herein. The window component625may be configured as or otherwise support a means for receiving a random access response from a second network node during a random access window associated with a random access request by the first network node. The UE type component630may be configured as or otherwise support a means for determining that the random access response is associated with a first UE type. The random access response component635may be configured as or otherwise support a means for decoding a transport block of the random access response based on the determination and the first network node being the first UE type.

Additionally, or alternatively, the communications manager620may support wireless communication at a first network node (e.g., the device605) in accordance with examples as disclosed herein. The control message component640may be configured as or otherwise support a means for receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types. The UE type component630may be configured as or otherwise support a means for determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The selection component645may be configured as or otherwise support a means for selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources. The random access request component650may be configured as or otherwise support a means for transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

Additionally, or alternatively, the communications manager620may support wireless communication at a first network node (e.g., the device605) in accordance with examples as disclosed herein. The control message component640may be configured as or otherwise support a means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. The UE type component630may be configured as or otherwise support a means for determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The selection component645may be configured as or otherwise support a means for selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts. The random access request component650may be configured as or otherwise support a means for transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

FIG.7shows a block diagram700of a communications manager720that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The communications manager720may be an example of aspects of a communications manager520, a communications manager620, or both, as described herein. The communications manager720, or various components thereof, may be an example of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager720may include a window component725, a UE type component730, a random access response component735, a control message component740, a selection component745, a random access request component750, a mapping component755, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager720may support wireless communication at a first network node in accordance with examples as disclosed herein. The window component725may be configured as or otherwise support a means for receiving a random access response from a second network node during a random access window associated with a random access request by the first network node. The UE type component730may be configured as or otherwise support a means for determining that the random access response is associated with a first UE type. The random access response component735may be configured as or otherwise support a means for decoding a transport block of the random access response based on the determination and the first network node being the first UE type.

In some examples, to support determining that the random access response is associated with the first UE type, the random access response component735may be configured as or otherwise support a means for determining that the random access response includes a downlink control channel message that includes UE type information indicative of one or more UE types with which the downlink control channel message is associated, where the one or more UE types includes the first UE type.

In some examples, the UE type information includes respective UE type information for each respective UE type of the one or more UE types, and the mapping component755may be configured as or otherwise support a means for receiving mapping information that maps each respective UE type information of the UE type information to a respective UE type of the one or more UE types.

In some examples, to support receiving the mapping information, the mapping component755may be configured as or otherwise support a means for receiving a system information message or a handover command, where the system information message or the handover command includes the mapping information. In some examples, at least one of the respective UE type information of the UE type information corresponds to a group of different UE types.

In some examples, to support receiving the random access response from the second network node during the random access window, the window component725may be configured as or otherwise support a means for receiving the random access response after one or more other random access responses are received during the random access window.

In some examples, first information included in a first MCS level field in the downlink control channel message indicates that the random access response is associated with the first UE type. In some examples, second information included in a second MCS level field in the downlink control channel message indicates a MCS level for the transport block of the random access response.

In some examples, first information included in a first transport block scaling field in the downlink control channel message indicates that the random access response is associated with the first UE type. In some examples, second information included in a second transport block scaling field in the downlink control channel message indicates a transport block scaling value for the transport block of the random access response.

In some examples, to support determining that the random access response is associated with the first UE type, the UE type component730may be configured as or otherwise support a means for determining that the random access response includes a downlink control channel message that includes UE type information included in a MCS level field or in a transport block scaling field, the UE type information indicative of the first UE type.

In some examples, to support determining that the random access response is associated with the first UE type, the UE type component730may be configured as or otherwise support a means for determining that the random access response includes a CRC value that is scrambled by an RNTI that is associated with the first UE type. In some examples, the RNTI is based on an index value associated with the first UE type.

In some examples, the index value is one of a set of multiple index values. In some examples, each respective index value of the set of multiple index values is associated with a respective UE type of a set of multiple UE types. In some examples, the set of multiple UE types includes the first UE type. In some examples, the index value is non-zero. In some examples, the random access request component750may be configured as or otherwise support a means for transmitting, included in the random access request, an indication that the first network node is of the first UE type.

In some examples, the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type. In some examples, the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs. In some examples, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

Additionally, or alternatively, the communications manager720may support wireless communication at a first network node in accordance with examples as disclosed herein. The control message component740may be configured as or otherwise support a means for receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types. In some examples, the UE type component730may be configured as or otherwise support a means for determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The selection component745may be configured as or otherwise support a means for selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources. The random access request component750may be configured as or otherwise support a means for transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

In some examples, the ranking prioritizes PRACH resources associated with a second UE type when none of the one or more PRACH resources included in the control message are associated with the first UE type. In some examples, the ranking prioritizes a default PRACH resource when none of the one or more PRACH resources included in the control message are associated with the first UE type and none of the one or more PRACH resources included in the control message are associated with the second UE type. In some examples, the ranking prioritizes PRACH resources associated with a third UE type when none of the one or more PRACH resources included in the control message are associated with the first UE type and none of the one or more PRACH resources included in the control message are associated with the second UE type.

In some examples, the second UE type is a RedCap UE type and the third UE type is an eMBB UE type. In some examples, the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type. In some examples, the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs. In some examples, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

In some examples, the control message component740may be configured as or otherwise support a means for receiving a second control message indicating the ranking for the PRACH resource selection.

Additionally, or alternatively, the communications manager720may support wireless communication at a first network node in accordance with examples as disclosed herein. The control message component740may be configured as or otherwise support a means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. In some examples, the UE type component730may be configured as or otherwise support a means for determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The selection component745may be configured as or otherwise support a means for selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts. The random access request component750may be configured as or otherwise support a means for transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

In some examples, the ranking prioritizes initial bandwidth parts associated with a second UE type when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type. In some examples, the ranking prioritizes a default initial bandwidth part when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type and none of the one or more initial bandwidth parts included in the control message are associated with the second UE type. In some examples, the ranking prioritizes initial bandwidth parts associated with a third UE type when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type and none of the one or more initial bandwidth parts included in the control message are associated with the second UE type.

In some examples, the second UE type is a RedCap UE type and the third UE type is an eMBB UE type. In some examples, the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type. In some examples, the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs. In some examples, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

In some examples, the control message component740may be configured as or otherwise support a means for receiving a second control message indicating the ranking for the initial bandwidth part selection.

FIG.8shows a diagram of a system800including a device805that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The device805may be an example of or include the components of a device505, a device605, or a UE115as described herein. The device805may communicate (e.g., wirelessly) with one or more network entities105, one or more UEs115, or any combination thereof. The device805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager820, an input/output (I/O) controller810, a transceiver815, an antenna825, a memory830, code835, and a processor840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus845).

The communications manager820may support wireless communication at a first network node (e.g., the device805) in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for receiving a random access response from a second network node during a random access window associated with a random access request by the first network node. The communications manager820may be configured as or otherwise support a means for determining that the random access response is associated with a first UE type. The communications manager820may be configured as or otherwise support a means for decoding a transport block of the random access response based on the determination and the first network node being the first UE type.

Additionally, or alternatively, the communications manager820may support wireless communication at a first network node (e.g., the device805) in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. The communications manager820may be configured as or otherwise support a means for determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The communications manager820may be configured as or otherwise support a means for selecting, in accordance with a rule for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node. The communications manager820may be configured as or otherwise support a means for transmitting a random access request to the second network node via the selected one of the one or more initial bandwidth parts.

By including or configuring the communications manager820in accordance with examples as described herein, the device805may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

The communications manager920, the receiver910, the transmitter915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager920may support wireless communication at first network node (e.g., the device905) in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for receiving a random access request from a second network node. The communications manager920may be configured as or otherwise support a means for determining that the second network node is associated with a first UE type. The communications manager920may be configured as or otherwise support a means for transmitting, based on the second network node being associated with the first UE type, a random access response in response to the random access request, the random access response indicative that the random access response is for UEs of the first UE type.

By including or configuring the communications manager920in accordance with examples as described herein, the device905(e.g., a processor controlling or otherwise coupled with the receiver910, the transmitter915, the communications manager920, or a combination thereof) may support techniques for more efficient utilization of communication resources.

The device1005, or various components thereof, may be an example of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager1020may include a request component1025, a UE type determination component1030, a random access component1035, or any combination thereof. The communications manager1020may be an example of aspects of a communications manager920as described herein. In some examples, the communications manager1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1020may support wireless communication at first network node (e.g., the device1005) in accordance with examples as disclosed herein. The request component1025may be configured as or otherwise support a means for receiving a random access request from a second network node. The UE type determination component1030may be configured as or otherwise support a means for determining that the second network node is associated with a first UE type. The random access component1035may be configured as or otherwise support a means for transmitting, based on the second network node being associated with the first UE type, a random access response in response to the random access request, the random access response indicative that the random access response is for UEs of the first UE type.

FIG.11shows a block diagram1100of a communications manager1120that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The communications manager1120may be an example of aspects of a communications manager920, a communications manager1020, or both, as described herein. The communications manager1120, or various components thereof, may be an example of means for performing various aspects of random access response schemes for eRedCap UEs as described herein. For example, the communications manager1120may include a request component1125, a UE type determination component1130, a random access component1135, a UE type information component1140, a CRC component1145, a mapping information component1150, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity105, between devices, components, or virtualized components associated with a network entity105), or any combination thereof.

The communications manager1120may support wireless communication at first network node in accordance with examples as disclosed herein. The request component1125may be configured as or otherwise support a means for receiving a random access request from a second network node. The UE type determination component1130may be configured as or otherwise support a means for determining that the second network node is associated with a first UE type. The random access component1135may be configured as or otherwise support a means for transmitting, based on the second network node being associated with the first UE type, a random access response in response to the random access request, the random access response indicative that the random access response is for UEs of the first UE type.

In some examples, the random access component1135may be configured as or otherwise support a means for including, as part of the random access response, a downlink control channel message that includes UE type information indicative of one or more UE types with which the downlink control channel message is associated, where the one or more UE types includes the first UE type.

In some examples, the UE type information includes respective UE type information for each respective UE type of the one or more UE types, and the mapping information component1150may be configured as or otherwise support a means for transmitting mapping information that maps each respective UE type information of the UE type information to a respective UE type of the one or more UE types.

In some examples, to support transmitting the mapping information, the mapping information component1150may be configured as or otherwise support a means for transmitting a system information message or a handover command, where the system information message or the handover command includes the mapping information. In some examples, at least one of the respective UE type information of the UE type information corresponds to a group of different UE types.

In some examples, to support transmitting the random access response, the random access component1135may be configured as or otherwise support a means for transmitting the random access response during a random access window after transmission of one or more other random access responses during the random access window.

In some examples, first information included in a first MCS level field in the downlink control channel message indicates that the random access response is associated with the first UE type. In some examples, second information included in a second MCS level field in the downlink control channel message indicates a MCS level for a transport block of the random access response.

In some examples, first information included in a first transport block scaling field in the downlink control channel message indicates that the random access response is associated with the first UE type. In some examples, second information included in a second transport block scaling field in the downlink control channel message indicates a transport block scaling value for a transport block of the random access response.

In some examples, the UE type information component1140may be configured as or otherwise support a means for including, as part of the random access response, a downlink control channel message that includes UE type information included in a MCS level field or in a transport block scaling field, the UE type information indicative of the first UE type.

In some examples, the CRC component1145may be configured as or otherwise support a means for scrambling a CRC value of the random access response using an RNTI that is associated with the first UE type. In some examples, the RNTI is based on an index value associated with the first UE type.

In some examples, the index value is one of a set of multiple index values. In some examples, each respective index value of the set of multiple index values is associated with a respective UE type of a set of multiple UE types. In some examples, the set of multiple UE types includes the first UE type. In some examples, the index value is non-zero.

In some examples, to support determining that the second network node is associated with the first UE type, the request component1125may be configured as or otherwise support a means for receiving, included in the random access request, an indication that the second network node is of the first UE type.

In some examples, the first UE type is an eRedCap UE type corresponding to reduced capabilities with respect to a RedCap UE type and an eMBB UE type. In some examples, the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs. In some examples, the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

FIG.12shows a diagram of a system1200including a device1205that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The device1205may be an example of or include the components of a device905, a device1005, or a network entity105as described herein. The device1205may communicate with one or more network entities105, one or more UEs115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device1205may include components that support outputting and obtaining communications, such as a communications manager1220, a transceiver1210, an antenna1215, a memory1225, code1230, and a processor1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1240).

The transceiver1210may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver1210may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver1210may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device1205may include one or more antennas1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver1210may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas1215, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas1215, from a wired receiver), and to demodulate signals. In some implementations, the transceiver1210may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas1215that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas1215that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver1210may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver1210, or the transceiver1210and the one or more antennas1215, or the transceiver1210and the one or more antennas1215and one or more processors or memory components (for example, the processor1235, or the memory1225, or both), may be included in a chip or chip assembly that is installed in the device1205. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link125, a backhaul communication link120, a midhaul communication link162, a fronthaul communication link168).

The memory1225may include RAM and ROM. The memory1225may store computer-readable, computer-executable code1230including instructions that, when executed by the processor1235, cause the device1205to perform various functions described herein. The code1230may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1230may not be directly executable by the processor1235but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1225may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1235may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor1235may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1235. The processor1235may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1225) to cause the device1205to perform various functions (e.g., functions or tasks supporting random access response schemes for eRedCap UEs). For example, the device1205or a component of the device1205may include a processor1235and memory1225coupled with the processor1235, the processor1235and memory1225configured to perform various functions described herein. The processor1235may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code1230) to perform the functions of the device1205. The processor1235may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device1205(such as within the memory1225). In some implementations, the processor1235may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device1205). For example, a processing system of the device1205may refer to a system including the various other components or subcomponents of the device1205, such as the processor1235, or the transceiver1210, or the communications manager1220, or other components or combinations of components of the device1205. The processing system of the device1205may interface with other components of the device1205, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device1205may include a processing system and one or more interfaces to output information, or to obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device1205may transmit information output from the chip or modem. Additionally, or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device1205may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that a first interface also may obtain information or signal inputs, and a second interface also may output information or signal outputs.

In some examples, a bus1240may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus1240may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device1205, or between different components of the device1205that may be co-located or located in different locations (e.g., where the device1205may refer to a system in which one or more of the communications manager1220, the transceiver1210, the memory1225, the code1230, and the processor1235may be located in one of the different components or divided between different components).

The communications manager1220may support wireless communication at first network node (e.g., the device1205) in accordance with examples as disclosed herein. For example, the communications manager1220may be configured as or otherwise support a means for receiving a random access request from a second network node. The communications manager1220may be configured as or otherwise support a means for determining that the second network node is associated with a first UE type. The communications manager1220may be configured as or otherwise support a means for transmitting, based on the second network node being associated with the first UE type, a random access response in response to the random access request, the random access response indicative that the random access response is for UEs of the first UE type.

By including or configuring the communications manager1220in accordance with examples as described herein, the device1205may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

In some examples, the communications manager1220may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver1210, the one or more antennas1215(e.g., where applicable), or any combination thereof. Although the communications manager1220is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1220may be supported by or performed by the transceiver1210, the processor1235, the memory1225, the code1230, or any combination thereof. For example, the code1230may include instructions executable by the processor1235to cause the device1205to perform various aspects of random access response schemes for eRedCap UEs as described herein, or the processor1235and the memory1225may be otherwise configured to perform or support such operations.

FIG.13shows a flowchart illustrating a method1300that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The operations of the method1300may be implemented by a UE or its components as described herein. For example, the operations of the method1300may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. In the example ofFIG.13, the UE is referred to as a first network node.

At1305, the method may include receiving a random access response from a second network node during a random access window associated with a random access request by the first network node. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by a window component725as described with reference toFIG.7.

At1310, the method may include determining that the random access response is associated with a first UE type. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by a UE type component730as described with reference toFIG.7.

At1315, the method may include decoding a transport block of the random access response based on the determination and the first network node being the first UE type. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a random access response component735as described with reference toFIG.7.

FIG.14shows a flowchart illustrating a method1400that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The operations of the method1400may be implemented by a UE or its components as described herein. For example, the operations of the method1400may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. In the example ofFIG.14, the UE is referred to as a first network node.

At1405, the method may include receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by a control message component740as described with reference toFIG.7.

At1410, the method may include determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a UE type component730as described with reference toFIG.7.

At1415, the method may include selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, where the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a selection component745as described with reference toFIG.7.

At1420, the method may include transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources. The operations of1420may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1420may be performed by a random access request component750as described with reference toFIG.7.

FIG.15shows a flowchart illustrating a method1500that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The operations of the method1500may be implemented by a UE or its components as described herein. For example, the operations of the method1500may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. In the example ofFIG.15, the UE is referred to as a first network node.

At1505, the method may include receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by a control message component740as described with reference toFIG.7.

At1510, the method may include determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, where the first network node is of the first UE type, and where the first UE type is an eRedCap UE type. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a UE type component730as described with reference toFIG.7.

At1515, the method may include selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, where the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a selection component745as described with reference toFIG.7.

At1520, the method may include transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts. The operations of1520may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1520may be performed by a random access request component750as described with reference toFIG.7.

FIG.16shows a flowchart illustrating a method1600that supports random access response schemes for eRedCap UEs in accordance with one or more aspects of the present disclosure. The operations of the method1600may be implemented by a network entity or its components as described herein. For example, the operations of the method1600may be performed by a network entity as described with reference toFIGS.1through4and9through12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include receiving a random access request from a second network node. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by a request component1125as described with reference toFIG.11.

At1610, the method may include determining that the second network node is associated with a first UE type. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a UE type determination component1130as described with reference toFIG.11.

At1615, the method may include transmitting, based on the second network node being associated with the first UE type, a random access response in response to the random access request, the random access response indicative that the random access response is for UEs of the first UE type. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a random access component1135as described with reference toFIG.11.

Aspect 1: A method of wireless communication performed by a first network node, comprising: receiving a control message indicating one or more PRACH resources to be used for random access of a second network node, each of the one or more PRACH resources being associated with a respective one or more UE types; determining that none of the one or more PRACH resources included in the control message are associated with a first UE type, wherein the first network node is of the first UE type, and wherein the first UE type is an eRedCap UE type; selecting, in accordance with a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message are associated with the first UE type, a particular PRACH resource of the one or more PRACH resources included in the control message for transmission of a random access preamble to the second network node, wherein the ranking is based on a respective UE type associated with each PRACH resource of the one or more PRACH resources; and transmitting the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

Aspect 2: The first network node of aspect 1, wherein the ranking prioritizes PRACH resources associated with a second UE type when none of the one or more PRACH resources included in the control message are associated with the first UE type.

Aspect 3: The first network node of aspect 2, wherein the ranking prioritizes a default PRACH resource when none of the one or more PRACH resources included in the control message are associated with the first UE type and none of the one or more PRACH resources included in the control message are associated with the second UE type.

Aspect 4: The first network node of aspect 2, wherein the ranking prioritizes PRACH resources associated with a third UE type when none of the one or more PRACH resources included in the control message are associated with the first UE type and none of the one or more PRACH resources included in the control message are associated with the second UE type.

Aspect 5: The first network node of aspect 4, wherein the second UE type is a RedCap UE type and the third UE type is an eMBB UE type.

Aspect 6: The first network node of any of aspects 1 through 5, wherein the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type.

Aspect 7: The first network node of any of aspects 1 through 6, wherein the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs.

Aspect 8: The first network node of aspect 7, wherein the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

Aspect 9: The method of any of aspects 1 through 8, further comprising: receiving a second control message indicating the ranking for the PRACH resource selection.

Aspect 10: A method of wireless communication performed by a first network node, comprising: receiving a control message indicating one or more initial bandwidth parts to be used for random access of a second network node, each of the one or more initial bandwidth parts being associated with a respective one or more UE types; determining that none of the one or more initial bandwidth parts included in the control message are associated with a first UE type, wherein the first network node is of the first UE type, and wherein the first UE type is an eRedCap UE type; selecting, in accordance with a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type, a particular initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with the second network node, wherein the ranking is based on a respective UE type associated with each initial bandwidth part of the one or more initial bandwidth parts; and transmitting a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

Aspect 11: The first network node of aspect 10, wherein the ranking prioritizes initial bandwidth parts associated with a second UE type when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type.

Aspect 12: The first network node of aspect 11, wherein the ranking prioritizes a default initial bandwidth part when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type and none of the one or more initial bandwidth parts included in the control message are associated with the second UE type.

Aspect 13: The first network node of aspect 11, wherein the ranking prioritizes initial bandwidth parts associated with a third UE type when none of the one or more initial bandwidth parts included in the control message are associated with the first UE type and none of the one or more initial bandwidth parts included in the control message are associated with the second UE type.

Aspect 14: The first network node of aspect 13, wherein the second UE type is a RedCap UE type and the third UE type is an eMBB UE type.

Aspect 15: The first network node of any of aspects 10 through 14, wherein the eRedCap UE type corresponds to reduced capabilities with respect to a RedCap UE type and an eMBB UE type.

Aspect 16: The first network node of any of aspects 10 through 15, wherein the first UE type is associated with a first maximum bandwidth processing capability that is lower than a second maximum bandwidth processing capability associated with eMBB UEs.

Aspect 17: The first network node of aspect 16, wherein the first maximum bandwidth processing capability pertains to one or more combinations of radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

Aspect 18: The method of any of aspects 10 through 17, further comprising: receiving a second control message indicating the ranking for the initial bandwidth part selection.

Aspect 19: A first network node comprising a processing system configured to perform a method of any of aspects 1 through 9.

Aspect 20: A first network node comprising at least one means for performing a method of any of aspects 1 through 9.

Aspect 21: A non-transitory computer-readable medium having code for wireless communication stored thereon that, when executed by a network node, causes the network node to perform a method of any of aspects 1 through 9.

Aspect 22: A first network node comprising a processing system configured to perform a method of any of aspects 10 through 18.

Aspect 23: A first network node comprising at least one means for performing a method of any of aspects 10 through 18.

Aspect 24: A non-transitory computer-readable medium having code for wireless communication stored thereon that, when executed by a network node, causes the network node to perform a method of any of aspects 10 through 18.

The methods described herein describe possible implementations, and the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

As used herein, the term “or” is an inclusive “or” unless limiting language is used relative to the alternatives listed. For example, reference to “X being based on A or B” shall be construed as including within its scope X being based on A, X being based on B, and X being based on A and B. In this regard, reference to “X being based on A or B” refers to “at least one of A or B” or “one or more of A or B” due to “or” being inclusive. Similarly, reference to “X being based on A, B, or C” shall be construed as including within its scope X being based on A, X being based on B, X being based on C, X being based on A and B, X being based on A and C, X being based on B and C, and X being based on A, B, and C. In this regard, reference to “X being based on A, B, or C” refers to “at least one of A, B, or C” or “one or more of A, B, or C” due to “or” being inclusive. As an example of limiting language, reference to “X being based on only one of A or B” shall be construed as including within its scope X being based on A as well as X being based on B, but not X being based on A and B. Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently. Also, as used herein, the phrase “a set” shall be construed as including the possibility of a set with one member. That is, the phrase “a set” shall be construed in the same manner as “one or more” or “at least one of”

The description set forth herein, in connection with the drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “aspect” or “example” used herein means “serving as an aspect, example, instance, or illustration,” and not “preferred” or “advantageous over other aspects.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.