Random access response scheme for enhanced reduced capability (RedCap) user equipment

Abstract

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

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 18 / 481,118, filed by ISLAM et al. on October 4, 2023, entitled “RANDOMACCESSRESPONSE SCHEMES FOR ENHANCED REDUCED CAPABILITY (REDCAP) USER EQUIPMENT”, which claims the benefit of U.S. Provisional Patent Application No. 63 / 414,376, filed by ISLAM et al. on October 7, 2022, entitled “RANDOMACCESSRESPONSE SCHEMES FOR ENHANCED REDUCED CAPABILITY (REDCAP) USER EQUIPMENT”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Background Art

[0003] The following relates to wireless communications related to a random access response scheme for enhanced reduced capability (eRedCap) user equipment (UE).

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described techniques relate to methods, systems, devices, and apparatuses that support a random access response scheme for an enhanced reduced capability (eRedCap) user equipment (UE). For example, the described techniques support receiving a random access response at a first network node 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 of 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.

[0006] 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 corresponding 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 belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering 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, wherein the ordering is based on the corresponding UE type associated with each of the one or more PRACH resources; and sending the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0007] 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 corresponding one or more UE types; determine that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; select a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, wherein the ordering is based on the corresponding UE type associated with each of the one or more PRACH resources; and send the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0008] Another first network node is described. The first network node may include: a component 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 corresponding one or more UE types; a component for: determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; a component for: selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, wherein the ordering is based on a corresponding UE type associated with each of the one or more PRACH resources; and a component for: sending the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0009] A non-transitory computer-readable medium having stored thereon code for wireless communication 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 corresponding 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, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; select a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering 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, wherein the ordering is based on the corresponding UE type associated with each of the one or more PRACH resources; and send the random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0010] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the ordering 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.

[0011] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, when the one or more PRACH resources included in the control message may not be associated with the first UE type and the one or more PRACH resources included in the control message may not be associated with the second UE type, the sorting will default to PRACH resource priority.

[0012] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, when the one or more PRACH resources included in the control message may not be associated with the first UE type and the one or more PRACH resources included in the control message may not be associated with the second UE type, the ordering prioritizes PRACH resources associated with a third UE type.

[0013] In some examples of the methods, first network nodes, and non-transitory computer-readable media 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.

[0014] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the eRedCap UE type corresponds to reduced capabilities relative to the RedCap UE type and the eMBB UE type.

[0015] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the first UE type may be associated with a first maximum bandwidth handling capability that may be lower than a second maximum bandwidth handling capability associated with the eMBBUE.

[0016] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the first maximum bandwidth processing capability is related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH).

[0017] Some examples of the methods, first network nodes, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control message indicating the ranking for the PRACH resource selection.

[0018] 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 corresponding one or more UE types; determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; selecting a specific 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 according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ordering is based on the corresponding UE type associated with each of the one or more initial bandwidth parts; and sending a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

[0019] 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 corresponding one or more UE types; determine that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; select a specific 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 according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ordering is based on the corresponding UE type associated with each of the one or more initial bandwidth parts; and send a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

[0020] 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 corresponding one or more UE types; means for determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; means for selecting a specific 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 according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ordering is based on a corresponding UE type associated with each of the one or more initial bandwidth parts; and means for sending a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

[0021] A non-transitory computer-readable medium having stored thereon code for wireless communication 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 corresponding one or more UE types; determine that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; select a specific 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 according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ordering is based on the corresponding UE type associated with each of the one or more initial bandwidth parts; and send a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

[0022] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the ordering prioritizes initial bandwidth portions associated with a second UE type when none of the one or more initial bandwidth portions included in the control message may be associated with the first UE type.

[0023] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, when the one or more initial bandwidth parts included in the control message may not be associated with the first UE type and the one or more initial bandwidth parts included in the control message may not be associated with the second UE type, the sorting will default to initial bandwidth part priority.

[0024] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, when the one or more initial bandwidth portions included in the control message may not be associated with the first UE type and the one or more initial bandwidth portions included in the control message may not be associated with the second UE type, the sorting prioritizes the initial bandwidth portion associated with the third UE type.

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

[0026] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the eRedCap UE type corresponds to reduced capabilities relative to the RedCap UE type and the eMBB UE type.

[0027] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the first UE type may be associated with a first maximum bandwidth handling capability that may be lower than a second maximum bandwidth handling capability associated with the eMBBUE.

[0028] In some examples of the methods, first network nodes, and non-transitory computer-readable media described herein, the first maximum bandwidth handling capability is related to one or more combinations of: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0029] Some examples of the methods, first network nodes, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control message indicating the ordering for the initial bandwidth portion selection. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 and Figure 2 Each illustrates an example of a wireless communication system supporting a random access response scheme for enhanced reduced capability (eRedCap) user equipment (UE) according to one or more aspects of the present disclosure.

[0031] Figure 3 and Figure 4 Each illustrates an example of a process flow for supporting a random access response scheme for enhanced RedCap (eRedCap) UE according to one or more aspects of the present disclosure.

[0032] Figure 5 and Figure 6 A block diagram of a device supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is shown.

[0033] Figure 7 A block diagram of a communications manager supporting a random access response scheme for eRedCap UEs is shown in accordance with one or more aspects of the present disclosure.

[0034] Figure 8 A diagram of a system including a device supporting a random access response scheme for eRedCap UEs is shown in accordance with one or more aspects of the present disclosure.

[0035] Fig. 9 and Fig.10 A block diagram of a device supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is shown.

[0036] Fig.11 A block diagram of a communications manager supporting a random access response scheme for eRedCap UEs is shown in accordance with one or more aspects of the present disclosure.

[0037] Fig.12 A diagram of a system including a device supporting a random access response scheme for eRedCap UEs is shown in accordance with one or more aspects of the present disclosure.

[0038] Figures 13 to 16 A flow chart illustrating a method of supporting a random access response scheme for eRedCap UEs according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0039] Some wireless communication systems may support multiple types of communication devices, such as user equipment (UE). For example, a wireless communication system may include a higher capability UE that supports relatively low latency and relatively high data throughput communications, such as enhanced mobile broadband (eMBB) communications. Such UEs may be referred to as eMBB UEs. Additionally or alternatively, a wireless communication system may include lower capability UEs or reduced capability (RedCap) UEs that may operate with one or more of reduced transmit power, a reduced number of transmit or receive antennas, a reduced transmit or receive bandwidth, or reduced computational complexity. Thus, some RedCap UEs may support reduced peak data throughput, reduced reliability, reduced bandwidth, or reduced other features or capabilities. In some examples, such as to support low-level Internet of Things (IoT) functionality, a wireless communication system may also include eRedCap (enhanced RedCap, which may also be referred to as evolved RedCap) UEs that have capabilities that may be reduced relative to RedCap UEs. Although reference is made throughout this disclosure to eRedCap UEs, it should be understood that the techniques described herein may also be applicable to other types of devices associated with bandwidth handling capabilities that may be reduced relative to bandwidth handling capabilities associated with eMBB UEs.

[0040] In some examples, eMBB UE, RedCap UE, eRedCap UE and other UE types may use the same set of time-frequency resources to send one or more messages as part of a random access process for establishing a connection with a network entity. Such resources may be referred to as random access opportunities. For example, eMBB UE, RedCap UE and eRedCap UE may use the same random access opportunity to send a random access request to a network entity. In such an example, each random access request may include a preamble selected at a corresponding UE (e.g., a UE that sends the random access request). In response, the network entity may send a random access response to one or more of the UEs. The random access response may include an identifier of the UE (e.g., an eMBB UE, a RedCap UE or an eRedCap UE) that sent the random access request in its payload. For example, the random access response may include (e.g., indicate) an identifier corresponding to a preamble sent from an eRedCap UE. However, in some examples, the bandwidth supported at the eRedCap UE may be constrained, such that the eRedCap UE may not be able to determine that a response is sent or that the response may be intended for an eRedCap UE. That is, the eRedCap UE may not be able to successfully decode the random access response. In such an example, the eRedCap UE may unnecessarily resend the preamble to the network entity, which may cause reduced resource utilization within the wireless communication system.

[0041] Various aspects of the present disclosure relate generally to techniques for random access response schemes for eRedCap UEs, and more particularly to schemes for sending random access responses to multiple UE types supporting 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 use one or more bits (e.g., reserved bits) in a field of the downlink control channel message to indicate the UE type. 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.

[0042] 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 the 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 the cyclic redundancy check (CRC) bits included in the downlink control channel message. Thus, the eRedCap UE and one or more other UEs may determine the 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 UE type (e.g., a different UE type or the same UE type). In some examples, the eRedCap UE may select a bandwidth part to be used for a random access procedure with the network entity (e.g., for sending a random access request) from the configured initial bandwidth part. 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.

[0043] Certain aspects of the subject matter described herein may be implemented to achieve 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 the eRedCap UE. In some examples, the operations performed by the described communication devices may also support other benefits such as reduced power consumption, increased throughput, and higher data rates.

[0044] Aspects of the disclosure are first described in the context of wireless communication systems and process flows. Aspects of the disclosure are also illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to a random access response scheme for an eRedCap UE.

[0045] Figure 1 An example of a wireless communication system 100 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0046] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0048] 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, may be, or may be included in (e.g., as 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 backhaul (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, the network node may be a UE. For another example, the network node may be a base station or a network entity. For 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 network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a 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 the present disclosure, once a specific example is expanded according to the present 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), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example 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 configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0049] 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, may be similar to, may include, or may be included in (e.g., is a component of) a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a reduced capability (Redcap) device, an enhanced reduced capability (eRedCap) device, an environmental 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 backhaul (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. For another example, a network entity may be a base station. As used herein, a "network entity" may refer to an entity configured to operate in a network, such as the network entity 105. For example, a "network entity" is not limited to an entity currently located in a network and / or currently operating in a network. Rather, a network entity may be any entity capable of communicating and / or operating in a network.

[0050] The adjectives "first", "second", "third", etc. are used in conjunction with a discussion to contextually distinguish between two or more modified nouns and are not meant to be absolute modifiers that apply only to specific corresponding entities throughout the document. For example, a network entity may be referred to as a "first network entity" in conjunction with one discussion and may be referred to as a "second network entity" in conjunction with another discussion, and 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 the 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 the 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 the example, the first network entity, the second network entity, and the third network entity may be different relative to these examples.

[0051] Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as network entities. For example, a 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 the present disclosure, once a specific example is expanded according to the present 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), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example 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, the first network entity may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network entity may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

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

[0053] As shown, a network entity (e.g., network entity 105) may include a processing system 106. Similarly, a network entity (e.g., UE 115) may include a processing system 112. A processing system may include one or more components (or subcomponents), such as one or more components described herein. For example, a corresponding component in the one or more components may be the following, similar to the following, including the following, or included in the following: 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 this example, the one or more components may include a first component, a second component, and a third component. In this example, a first component may be coupled to a second component and a third component. In this example, a first component may be at least one processor, a second component may be a communication interface, and a third component may be at least one memory. A processing system may generally be a system including one or more components that can 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 as 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 as output, such as a signal or any other information), and one or more components may perform any function as described herein or any combination thereof. As described herein, "input" and "input information" may be used interchangeably. Similarly, as described herein, "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 such as network entities 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., which is coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., a 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, wherein the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

[0054] The processing system of the network entity described herein may be docked with one or more other components of the network entity, may process information (such as input information) received from one or more other components, or may output the information to one or more other components. For example, the processing system may include a first component configured to dock 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., which is coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., a first communication interface or a second communication interface). For example, a chip or a modem of a network entity may include a processing system. The processing system may include a first communication interface for receiving or obtaining information, and a second communication interface for outputting, sending or providing 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 send 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, send or provide information.

[0055] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0056] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0057] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0058] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0059] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0060] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support a random access response scheme for an eRedCap UE as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0061] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0062] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0063] UE 115 and network entity 105 may use resources associated with one or more carriers to communicate wirelessly with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part) operating according to one or more physical layer channels of a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0064] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a bandwidth portion) or all of the carrier bandwidth.

[0065] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0066] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more bandwidth parts with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple bandwidth parts. In some examples, a single bandwidth part of a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active bandwidth parts.

[0067] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0068] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0069] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0070] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0071] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0072] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0073] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0074] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0075] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0076] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0077] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0079] The wireless communication system 100 may utilize both licensed radio frequency spectrum bands and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed radio frequency spectrum bands, devices such as network entities 105 and UEs 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0080] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

[0081] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0082] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0083] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0084] The wireless communication system 100 may support a scheme for sending random access responses to multiple UE types supporting multiple (e.g., different) bandwidths. For example, the network entity 105 may use a downlink control channel message included in the random access response to indicate the UE type associated with the random access response. In some examples, the UE 115 may receive the random access response from the network entity 105 during a random access window associated with the random access request of the UE 115. The UE 115 may determine that the random access response is associated with a first UE type. In such examples, the UE 115 may decode a transport block of the random access response based on the determination and that the UE 115 is a first UE type (e.g., an eRedCap UE).

[0085] Additionally or alternatively, UE 115 may receive a control message indicating one or more initial bandwidth parts to be used for random access of network entity 105, each of the one or more initial bandwidth parts being associated with a corresponding one or more UE types. In some examples, UE 115 may determine that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type (e.g., a first UE type corresponding to UE 115). In such examples, UE 115 may select a specific initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access procedure with network entity 105. In some examples, when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, UE 115 may select a specific initial bandwidth part according to a rule for initial bandwidth part selection. UE 115 may send a random access request to network entity 105 via the selected one of the one or more initial bandwidth parts. In some examples, sending a random access request using a selected one of the one or more initial bandwidth portions may result in improved efficiency associated with random access within the wireless communication system 100, among other possible benefits.

[0086] Figure 2 An example of a wireless communication system 200 that supports a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement one or more aspects of the wireless communication system 100 or may be implemented according to the one or more aspects. For example, the wireless communication system 200 may include a UE 215-a and a UE 215-b, which may be as described in reference Figure 1 The wireless communication system 200 may also include a network entity 205, which may be as described in reference Figure 1Examples of one or more of the network entities 105 (e.g., CU, DU, RU, base station, IAB node, or one or more other network nodes) are described. The network entity 205 and the UE 215 may communicate using the communication link 220-a and the communication link 220-b, which may be as described in reference Figure 1 An example of a communication link 125 is described. Figure 2 In the example of FIG. 1 , UE 215 and network entity 205 may communicate within coverage area 210, which may be as shown in FIG. Figure 1 An example of a depicted coverage area 110. Wireless communication system 200 may include features for improving communications between network entity 205 and UE 215, among other possible benefits.

[0087] The wireless communication system 200 may include multiple UE types, such as smart phones (e.g., enhanced mobile broadband (eMBB) UEs), one or more other vertical market UEs (e.g., ultra-reliable low latency communications (URLLC) UEs, V2X UEs), and other examples. Additionally or alternatively, to achieve scalability and enable deployment in a more efficient and cost-effective manner, the wireless communication system 200 (e.g., an NR system) may include another UE type with reduced capabilities. For example, the wireless communication system 200 may include one or more RedCap UEs. In some examples, the wireless communication system 200 may support RedCap UEs by relaxing peak throughput, latency, and reliability constraints. Figure 2 In the example, UE 215-a may be an example of an eMBB UE or a RedCap UE, which is an example of a non-eRedCap UE. In some examples, the RedCap UE may result in reduced cost, complexity, and power consumption, among other possible benefits. Additionally or alternatively, the wireless communication system 200 may support RedCap evolution, which may consider using another UE type with further reduced capabilities to support one or more low-layer IoT use cases. Such UEs may be referred to as eRedCap UEs. Figure 2 In the example of , UE 215-b may be an example of an eRedCap UE. For example, the wireless communication system 200 may support coexistence between non-eRedCap UEs (such as UE 215-a) and eRedCap UEs (such as UE 215-b).

[0088] In some examples, an eRedCap UE (e.g., an NR eRedCap UE) may be designed to reduce (e.g., minimize) UE complexity and reduce (e.g., further save) equipment costs. In such examples, the UE bandwidth may also be reduced relative to other UE types (e.g., from an NR baseline). For example, in order to reduce cost and complexity relative to UE 215-a, UE 215-b may support a reduced bandwidth or data rate (or both). That is, while an eMBB UE may support a bandwidth of approximately 100 MHz and a RedCap UE may support a bandwidth of approximately 20 MHz, for some communication channels, an eRedCap UE may support a bandwidth of approximately 5 MHz. For example, UE 215-b may support a baseband bandwidth reduction, wherein UE 215-b may use a baseband bandwidth of approximately 5 MHz for PDSCH (e.g., for both unicast and broadcast) and PUSCH. In some examples, UE 215-b may support a radio frequency bandwidth of approximately 20 MHz for one or more other channels (such as other uplink channels and other downlink channels). That is, the eRedCapUE may support a radio frequency bandwidth of approximately 20 MHz for baseband channels except for PDSCH and PUSCH.

[0089] In some examples, although the eRedCap UE and the non-eRedCap UE (e.g., RedCap UE or eMBB UE) may use multiple (e.g., different) preamble indexes for the RACH procedure (e.g., based on the indication of Msg1), the eRedCap UE and the non-eRedCap UE may share the same time-frequency position to send the corresponding preamble. The time-frequency position for sending the preamble may be referred to as a random access channel (RACH) opportunity, a physical random access channel (PRACH) opportunity, or a random access opportunity. In some examples, UE 215-a (e.g., a non-eRedCap UE) and UE 215-b (e.g., an eRedCap UE) may each perform a random access procedure to establish a connection with the network entity 205. In some examples, such as for a contention-based random access procedure, UE 215-a and UE 215-b may select a random access preamble (e.g., preamble 230-a and preamble 230-b, respectively) to send to the network entity 205. In some examples, UE 215-a and UE 215-b may include a corresponding preamble in a random access request. The random access request may correspond to a first message (e.g., Msg1) of a random access procedure. For example, UE 215-a and UE 215-b may use the random access request to send a preamble 230-a and a preamble 230-b to the network entity 205, respectively.

[0090] exist Figure 2In the example of , UE 215-a and UE 215-b may use the same PRACH opportunity to send preamble 230-a and preamble 230-b to network entity 205, respectively. In some examples, the transmission of the random access preamble may be referred to as PRACH transmission. In some examples, network entity 205 may select preamble 230-a or preamble 230-b to establish a connection to the corresponding UE. That is, network entity 205 may select preamble 230-a to establish a connection with UE 215-a, or select preamble 230-b to establish a connection with UE 215-b. Additionally or alternatively, network entity 205 may indicate the selected random access preamble to UE 215. For example, network entity 205 may send a random access response indicating the selected preamble to UE 215.

[0091] In response to receiving one or more random access requests, the network entity 205 may send a random access response, such as a random access response 265-a and a random access response 265-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 the same PRACH opportunity. For example, after the PRACH is sent during the PRACH opportunity, UE 215-a and UE 215-b may monitor the random access response (e.g., DCI) during a duration (e.g., a random access response window, such as which may be configured using a rar-WindowLength information element (IE) in a system information block (SIB) message). In some examples, UE 215-a may monitor the PDCCH during window 235-a, and UE 215-b may monitor the PDCCH during window 235-b. For example, UE 215-a and UE 215-b may monitor the PDCCH for a random access response grant, wherein the CRC bits included in the grant may be scrambled using a random access RNTI (RA-RNTI) corresponding to a PRACH transmission (e.g., a PRACH timing). In some examples, UE 215-a and UE 215-b may monitor the PDCCH for a DCI having a format (e.g., format 1_0) of CRC bits scrambled using a RA-RNTI corresponding to a PRACH timing. That is, in response to receiving preamble 230-a or preamble 230-b or both preamble 230-a and preamble 230-b, network entity 205 may use the PDCCH to send a random access response including grant 240-a and another random access response including grant 240-b. Grant 240-a and grant 240-b may be scrambled using a RA-RNTI associated with a PRACH opportunity in which preamble 230-a and preamble 230-b are sent from UE 215-a and UE 215-b, respectively. In this example, if UE 215-a and UE 215-b successfully detect (and decode) grant 240-a and grant 240-b, respectively, UE 215-a and UE 215-b may decode the corresponding PDSCH message carrying random access response data. For example, random access response 265-a may include grant 240-a and a payload 245-a corresponding to grant 240-a (e.g., a PDSCH message, a transport block carrying random access response data). In this example, if UE 215-a successfully decodes grant 240-a, UE 215-a may determine the decoded payload 245-a.Additionally or alternatively, if the UE 215-a successfully decodes the payload 245-a, the UE 215-a may proceed to send a third message (e.g., Msg3) of the random access procedure.

[0092] In some examples, such as for NR systems, the RA-RNTI may be determined (e.g., calculated) according to the following Equation 1:

[0093]

[0094] Where s_id may correspond to an index of a PRACH opportunity relative to the first OFDM symbol (e.g., 0≤s_id<14). Additionally or alternatively, t_id may correspond to an index of a PRACH opportunity relative to the first time slot in the system frame (e.g., 0≤t_id<80). In some examples, the subcarrier spacing used to determine t_id may be based on a value of a parameter (μ), which may be configured at the network entity 205 and the UE 215. In some examples, f_id may correspond to an index of a PRACH opportunity in the frequency domain (0≤f_id<8), and ul_carrier_id may correspond to an index of a PRACH opportunity in the frequency domain (0≤f_id<8). The uplink carrier used for PRACH transmission at 215-b (e.g., for a normal uplink (NUL) carrier, ul_carrier_id may correspond to a value of 0, and for a supplemental uplink (SUL) carrier, ul_carrier_id may correspond to a value of 1. In such examples, the RA-RNTI may be determined (e.g., calculated) regardless of the preamble identifier (ID) indicated using the random access response. That is, the RA-RNTI calculation may depend on the time-frequency position of the PRACH resource (e.g., the PRACH resource used for the PRACH transmission, the PRACH opportunity) The preamble ID may be set, but may not depend on the preamble ID of the PRACH sequence (e.g., the preamble indicated using the random access response). In some examples, the preamble ID may include a preamble index, such as may be indicated using an RRC parameter (e.g., the ra-PreambleIndex field of an IE sent using RRC signaling). In such examples, UEs that send random access requests (e.g., PRACH, preambles) at the same time-frequency position (e.g., using the same PRACH opportunity) may be able to decode the same random access response grant (e.g., RA-RNTI grant). For example, since the UE UE 215-a and UE 215-b use the same PRACH opportunity to send preamble 230-a and preamble 230-b, respectively, so UE 215-a and UE 215-b may be able to decode random access response grants that are scrambled using the same RA-RNTI (e.g., a RA-RNTI calculated based on the PRACH opportunity). In some examples, the ability to decode the random access response grant may be based on whether the UE has sufficient coverage to receive the random access response grant. That is, if UE 215 has sufficient coverage to receive the random access response grant, UE 215-a and UE 215-b may be able to decode the random access response grant (e.g., one or more grants 240).

[0095] In some examples, if UE 215 fails to successfully receive the payload included in the random access response grant, UE 215 may be configured to resend the preamble. For example, if UE 215-a and UE 215-b receive grant 240-a and grant 240-b and successfully decode both grants, UE 215-a and UE 215-b may attempt to decode the corresponding payload (e.g., payload 245-a and payload 245-b, respectively). In some examples, if UE 215-a and UE 215-b fail to decode the corresponding payload within window 235-a and window 235-b, respectively, UE 215-a and UE 215-b may determine to resend preamble 230. For example, UE 215-a may determine to resend preamble 230-a, and UE 215-b may determine to resend preamble 230-b. That is, if the UE fails to successfully receive (and decode) a payload (e.g., a transport block in the corresponding PDSCH) within the random access response window, one or more relatively higher layers (e.g., a protocol stack associated with the UE) may instruct the physical layer (e.g., a protocol stack associated with the UE) to send (or resend) the PRACH. In some examples, if the relatively higher layer requests, the UE may receive (or resend) the PRACH during a certain duration (e.g., not later than about N) after the relative last symbol of the window or the relative last symbol of the PDSCH reception. T,1 +0.75ms, where N T,1 The PRACH may be sent (or resent) corresponding to the duration of a symbol corresponding to the PDSCH processing time of the UE. That is, if the UE detects a random access grant (e.g., DCI scrambled via RA-RNTI) but fails to decode the corresponding payload (e.g., random access response payload, PDSCH message carrying random access response data), the UE may resend the PRACH before the window ends.

[0096] Additionally or alternatively, if the random access response payload (e.g., a PDSCH message, a transport block carrying random access response data) fails to include an ID corresponding to a preamble sent from the UE (e.g., a preamble ID selected at the UE), the UE may be configured to resend the preamble (e.g., a PRACH). For example, UE 215-b may determine that payload 245-b fails to include an ID corresponding to preamble 230-b. However, in some examples, a bandwidth 260-a used at network entity 205 to send payload 245-b may exceed a bandwidth 260-b supported at UE 215-b. For example, network entity 205 may use bandwidth 260-a (e.g., a bandwidth of approximately 20 MHz) to send payload 245-b (which may include an ID corresponding to preamble 230-b), and UE 215-b (e.g., an eRedCap UE) may support bandwidth 260-b (e.g., a bandwidth of approximately 5 MHz). For example, the bandwidth of the shared channel 255 that can be monitored at UE 215-b may correspond to bandwidth 260-b. In such an example, UE 215-b may not be able to successfully decode payload 245-b, and may determine to resend preamble 230-b regardless of payload 245-b including an ID corresponding to preamble 230-b. Additionally or alternatively, UE 215-a (e.g., a non-eRedCap UE, such as an eMBB UE or a RedCap UE) may support a bandwidth of approximately 20 MHz. Therefore, UE 215-a may successfully decode a payload sent from a network entity using bandwidth 260-a. That is, UE 215-a may support bandwidth 260-a, and UE 215-b may support bandwidth 260-b. In such an example, network entity 205 may not be able to send a random access response using a bandwidth supported at UE 215-a and UE 215-b. For example, the network entity 205 may not be able to determine how to transmit random access responses to two groups of UEs that may support multiple (eg, different) baseband bandwidths. Figure 2 The example illustrates grant 240 - b and payload 245 - b spanning bandwidth 260 - a , but it should be understood that grant 240 - b and payload 245 - b may span multiple different bandwidths, including bandwidth 260 - b .

[0097] In some examples, if both an eRedCap UE and a non-eRedCap UE (e.g., a RedCap UE or an eMBB UE) use the same PRACH opportunity to send PRACH, both the eRedCap UE and the non-eRedCap UE may be able to decode the corresponding random access response grant (e.g., if the eRedCap and non-eRedCap UEs have sufficient coverage). For example, since the preamble 230-a and the preamble 230-b are sent using the same PRACH opportunity, UE 215-a and UE 215-b may be able to decode grant 240-a and grant 240-b, respectively. In such an example, the non-eRedCap UE may be able to decode the corresponding random access response payload. However, due to the constrained shared channel bandwidth (e.g., since the eRedCap UE supports a PDSCH bandwidth of approximately 5 MHz), some eRedCap UEs may be unable to decode the corresponding random access response payload. For example, a group of eRedCap UEs with relatively good coverage may not be able to decode the random access response payload. In some examples, if the eRedCap UE fails to decode the random access response payload, the eRedCap UE may resend the PRACH regardless of the random access response payload including an ID corresponding to the preamble selected at the UE. For example, UE 215-a may be able to decode payload 245-a, but UE 215-b may not be able to decode payload 245-b. In such an example, UE 215-b may resend preamble 230-b regardless of whether payload 245-b includes an ID corresponding to preamble 230-b, which may cause an increase in random access (e.g., RACH) latency within the wireless communication system 200.

[0098] In some examples, UE 215-b may be able to indicate to network entity 205 that UE 215-b supports reduced capabilities (e.g., UE 215-b may be an eRedCap UE). For example, UE 215-b and network entity 205 may support one or more mechanisms for relatively early indication from UE 215-b that UE 215-b may be an eRedCap UE or one or more other UE types that may have reduced capabilities. In some examples, relatively early indication of an eRedCap UE (e.g., operating within wireless communication system 200) may be enabled by one or more schemes. For example, UE 215-b may use a message (e.g., Msg1) sent as part of a random access procedure to indicate that UE 215-b may be an eRedCap UE. That is, UE 215-b may support an early indication scheme based on Msg1. In some examples, UE 215-b may send a message (e.g., Msg1) using an initial bandwidth portion. In such an example, in response to receiving the message from UE 215-b, the network entity 205 may assign another initial bandwidth portion (e.g., a separate initial bandwidth portion) to UE 215-b. For example, the number of PRACH opportunities that can be included in the initial bandwidth portion may be constrained, and therefore, using different PRACH opportunities for multiple (e.g., different) UE types may be relatively expensive. Therefore, in some examples, the network entity 205 may assign different initial bandwidth portions to non-eRedCap UEs (e.g., UE 215-a) and eRedCap UEs (e.g., UE 215-b). In some other examples, the number of PRACH opportunities that can be included in the initial bandwidth portion may be applicable to multiple types of UEs. In such examples, the network entity 205 may assign an initial bandwidth portion that can be shared between non-eRedCap UEs (e.g., UE 215-a) and eRedCap UEs (e.g., UE 215-b). For example, in response to receiving an indication that UE 215-b may be an eRedCap UE, network entity 205 may assign to UE 215-b an initial bandwidth portion that may be shared with UE 215-a. In some examples, network entity 205 may assign multiple (e.g., separate) time-frequency locations for PRACH resources to be used at UE 215-a and UE 215-b. In some other examples, network entity 205 may assign the same time-frequency location for PRACH resources to be used at UE 215-a and UE 215-b. In such examples, network entity 205 may configure UE 215-a and UE 215-b with multiple sets (e.g., different sets) of preamble indexes.Additionally or alternatively, UE 215-b may use another message (e.g., Msg3) sent as part of the random access procedure to indicate that UE 215-b may be an eRedCap UE. For example, UE 215-b may support an early indication scheme based on Msg3.

[0099] In some examples, the wireless communication system 200 may support one or more random access response schemes for UEs with constrained bandwidth (such as, eRedCap UEs). For example, the network entity 205 may use a random access response grant to indicate the UE type associated with the random access response grant and the corresponding payload. Figure 2 As illustrated by the example of , UE 215-a and UE 215-b may receive one or more random access responses (e.g., each random access response includes a corresponding grant 240 and a corresponding payload 245) from network entity 205 during a random access window that may be associated with a random access request. For example, UE 215-a and UE 215-b may receive one or more random access responses from network entity 205 during window 235-a and window 235-b, respectively, which random access responses may be associated with preamble 230-a and preamble 230-b. In response to receiving the random access response from network entity 205, UE 215-a and / or UE 215-b may determine that the random access response is associated with a UE type, and may decode a transport block (e.g., payload 245) of the random access response based on the indicated UE type. For example, network entity 205 may include UE type indication 250 in grant 240-b. The UE type indication 250 may indicate to the UE 215-b a grant 240-b and a corresponding payload (e.g., payload 245-b) that may be associated with an eRedCap UE. For example, the UE type indication 250 may indicate that the payload 245-b may be sent using a reduced bandwidth, such as a bandwidth that may be supported at the UE 215-b (or one or more other eRedCap UEs). In such an example, the UE 215-b may determine to decode the payload 245-b based on the UE type indication 250 indicating the UE type corresponding to the UE 215-b.

[0100] In some examples, the network entity 205 may use one or more fields in the reserved bits of the random access response grant to indicate the UE type. For example, the network entity 205 may be able to use these fields to indicate whether the random access response grant (e.g., including the UE type indication) is applicable to eRedCap UEs. That is, the network entity 205 may use the fields included in the random access response grant to indicate whether the random access response grant is intended for eRedCap UEs or for one or more other UE types. Figure 2As illustrated in the example of , the network entity 205 may use one or more reserved bits (e.g., DCI) included in the grant 240-b to signal the UE type indication 250 to the UE 215-b. In some examples, in response to receiving the UE type indication 250, the UE 215-b (e.g., an eRedCap UE) may attempt to decode the random access response payload corresponding to the random access response grant. For example, the network entity 205 may use the reserved bits included in the grant 240-b to indicate that the payload 245-b is intended for eRedCap UEs (e.g., sent using a bandwidth suitable for eRedCap UEs). In such an example, the UE 215-b may attempt to decode the payload 245-b in response to determining (e.g., based on decoding the grant 240-b) that the payload 245-b is intended for an eRedCap UE. In some other examples, the UE 215-b may determine (e.g., based on decoding the grant 240-b) that the payload 245-b may be intended for another UE type. In such an example, UE 215-b may avoid decoding (e.g., reading) payload 245-b and monitor the PDSCH for one or more other random access response grants within window 235-b (e.g., continue to monitor the PDSCH, wait). That is, in such an example, the eRedCap UE may wait within the random access response window to receive another random access response grant that may be intended for the eRedCap UE. For example, UE 215-b may monitor (and receive) grant 240-c. In such an example, grant 240-c may include one or more reserved bits indicating that payload 245-c is intended for an eRedCap UE. In such an example, UE 215-b may attempt to decode (e.g., read) payload 245-c.

[0101] In some examples, to indicate the UE type to the eRedCap UE, the network entity 205 may transmit one or more random access response grants. For example, the network entity 205 may transmit the random access response grants twice or more. In such an example, the first random access response grant may be intended for a non-eRedCap UE (e.g., a RedCap UE or an eMBB UE), such as UE 215-a, and the second random access response grant may be intended for an eRedCap UE, such as UE 215-b. For example, the network entity may send grant 240-a and grant 240-b, which may be intended for UE 215-a and UE 215-b, respectively. In such an example, grant 240-b may include UE type indication 250.

[0102] For example, grant 240-b may be an example of a downlink control channel message that includes UE type information indicating one or more UE types that may be associated with the downlink control channel message (e.g., grant 240-b). That is, the network entity 205 may use the UE type indication 250 to indicate one or more UE types (such as, eRedCapUE) or one or more other UE types, such as one or more future UE types. In some examples, grant 240-b may include (e.g., in a field) one or more bits indicating one or more UE types associated with grant 240-b. That is, the UE type information (e.g., UE type indication 250) may be included in one or more bits in a field included in grant 240-b, and each of the one or more bits or multiple bits in the one or more bits may correspond to a corresponding UE type. Additionally or alternatively, each of the one or more bits or multiple bits in the one or more bits may correspond to a corresponding set of UE types. In some examples, the network entity 205 may use a plurality of reserved bits included in a grant 240-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 more UE types. In some examples, the same bit may be reserved for a plurality of different UE types. Additionally or alternatively, the network entity 205 may configure the UE 215 with mapping information associated with the reserved bits for indicating different UE types that may be configured via the network entity 205. That is, the mapping information may be used at the UE 215 to map each bit (or multiple bits) included in the field to a corresponding UE type. Additionally or alternatively, the mapping information may be used at the UE 215 to map each bit (or multiple bits) included in the field to a corresponding set of UE types. In some examples, the network entity 205 may send information associated with the mapping via system information or a handover command.

[0103] In some examples, a UE may receive a random access response grant that is not intended for the UE before receiving a random access response grant that is intended for the UE. For example, a network entity may send a first random access response grant for a non-eRedCap UE (e.g., a RedCap or eMBB UE) and a second random access response grant for an eRedCap UE. In such an example, if the eRedCap UE receives the first random access response grant (e.g., before the second random access response grant), the eRedCap UE may avoid 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 indicating a UE type other than the eRedCap UE (or fails to include a UE type indication). Additionally or alternatively, if the non-eRedCap UE receives the second random access response grant before the first random access response grant, the non-eRedCap UE may attempt to decode the corresponding payload. For example, a non-eRedCap UE may not be able to decode the bit included in the second random access response grant indicating that the corresponding payload is intended for an eRedCap UE.

[0104] like Figure 2As illustrated by the example of , UE 215-a may fail to receive (or fail to successfully decode, such as due to link coverage) a grant that may be intended for a non-eRedCap UE. Additionally or alternatively, UE 215-a may receive a grant intended for an eRedCap UE before receiving a grant intended for a non-eRedCap (e.g., RedCap or eMBB) UE. For example, UE 215-a may receive grant 240-a before receiving grant 240-d (e.g., which is associated with payload 245-d). In this example, grant 240-a may be intended for an eRedCap UE, and grant 240-d may be intended for a non-eRedCap UE. That is, grant 240-a may include one or more reserved bits indicating that the corresponding payload (e.g., payload 245-a) is intended for an eRedCap UE (or another UE type different from a RedCap UE or an eMBB UE). In such an example, UE 215-a may be unable to decode the one or more reserved bits and, therefore, may not be aware that payload 245-a is intended for an eRedCap UE. Therefore, UE 215-a may attempt to decode payload 245-a. In some examples, based on decoding payload 245-a, UE 215-a may determine that payload 245-a fails to include an identifier associated with preamble 230-a and may determine to resend preamble 230-a (e.g., unnecessarily) before receiving grant 240-d (e.g., a grant intended for a non-eRedCap UE).

[0105] In some examples, to avoid a situation where a non-eRedCap UE (e.g., a RedCap UE or an eMBB UE) can read a random access response grant (or a corresponding payload) intended for an eRedCap UE, the network entity 205 may include an indication for the eRedCap UE and the non-eRedCap UE. For example, the network entity 205 may use one or more of the multiple fields included in the random access response grant to indicate that the random access response grant is intended for an eRedCap UE and that the non-eRedCap UE is to avoid decoding the corresponding payload. In some examples, the network entity 205 may use an MCS field, a transport block scaling field, or both. For example, the network entity 205 may use a first MCS level field (e.g., a field decodable at a non-eRedCap UE) to indicate that the corresponding payload is intended for an eRedCap UE and that the non-eRedCap UE may avoid decoding the corresponding payload. In some examples, to indicate that the non-eRedCap UE is to avoid decoding the corresponding payload, the first MCS level field may indicate "reserved". For example, a non-eRedCap UE may determine an MCS reserved for a corresponding payload (e.g., a transport block) based on a first MCS level field indicating "reserved" included in a random access response grant. In such an example, the non-eRedCap UE may determine that the random access response grant is invalid and may avoid decoding (e.g., may ignore) the corresponding payload. Additionally or alternatively, the network entity 205 may use a second MCS level field included in a grant intended for eRedCap UEs to indicate an MCS level to be used for decoding the corresponding payload at the eRedCap UE. In some examples, the network entity 205 may include a second MCS level field (e.g., for eRedCap UEs) using a reserved bit included in a random access response grant (e.g., a PDCCH message such as a DCI).

[0106] exist Figure 2In the example of , the first MCS level field included in the grant 240-a may indicate that the random access response including the grant 240-a and the payload 245-a is associated with the eRedCap UE. Additionally or alternatively, the second MCS level field included in the grant 240-a may indicate the MCS level used for the payload 245-a. In this example, the UE 215-a may avoid decoding the payload 245-a (e.g., it may be determined that the grant 240-a is invalid). Additionally or alternatively, the first MCS level field included in the grant 240-b may indicate that the random access response including the grant 240-b and the payload 245-b is associated with the eRedCap UE. Additionally or alternatively, the second MCS level field included in the grant 240-b may indicate the MCS level used for the payload 245-b. In this example, the UE 215-b may use the indicated MCS level to decode the payload 245-b. In some examples, the first MCS level field may correspond to the UE type indication 250.

[0107] Additionally or alternatively, the network entity 205 may use the first transport block scaling field (e.g., a field decodable at a non-eRedCap UE) to indicate that the corresponding payload is intended for an eRedCap UE and that the non-eRedCap UE may avoid decoding the corresponding payload. In some examples, to indicate that the non-eRedCap UE is to avoid 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 the MCS reserved for the corresponding payload (e.g., transport block) based on the second transport block scaling field included in the random access response grant indicating "11" (which may correspond to a reservation). In such an example, the non-eRedCap UE may determine that the transport block scaling field is invalid and may avoid decoding (e.g., may ignore) the corresponding payload. Additionally or alternatively, the network entity 205 may use the second transport block scaling field included in the grant intended for the eRedCap UE to indicate to the eRedCap UE the transport block scaling for the corresponding payload. In some examples, the network entity 205 may use reserved bits included in a random access response grant (e.g., a PDCCH such as a DCI) to include a second transport block scaling field (e.g., for eRedCap UEs).

[0108] like Figure 2As illustrated in the example of , the first transport block scaling field included in grant 240-a may indicate that the random access response including grant 240-a and payload 245-a is associated with an eRedCap UE (e.g., the transport block scaling reserved for payload 245-a). In such an example, UE 215-a may avoid decoding payload 245-a (e.g., may determine that grant 240-a is invalid). Additionally or alternatively, the first transport block scaling field included in grant 240-b may indicate that the random access response including grant 240-b and payload 245-b is associated with an eRedCap UE. Additionally or alternatively, the second transport block scaling field included in grant 240-b may indicate the transport block scaling for payload 245-b. In such an example, UE 215-b may decode payload 245-b using the indicated transport block scaling. In some examples, the first transport block scaling field may correspond to UE type indication 250.

[0109] In some other examples, the network entity 205 may use the RA-RNTI to indicate the UE type associated with the random access response grant. For example, the RA-RNTI calculation may be combined with the UE type. In some examples, incorporating the UE type into the RA-RNTI calculation may enable the network entity 205 to send multiple (e.g., different) random access responses between different UE types (e.g., relatively smoothly). In some examples, the network entity 205 (e.g., and UE 215) may use one or more parameters to determine (e.g., calculate) the RA-RNTI. For example, the RA-RNTI may be determined according to the following equation 2 (e.g., which may take the form of the following equation):

[0110]

[0111] For a non-RedCap UE (e.g., an eMBB UE, a RedCap UE, or one or more other UE types), the parameter UE_type may correspond to a value of 0. Additionally or alternatively, for an eRedCap UE, the parameter UE_type may correspond to a value of 1. In some examples, for another UE type, the parameter UE_type may correspond to another value (e.g., a value different from 0 or 1). That is, multiple values ​​may be used to indicate multiple (e.g., different) UE types. Figure 2As illustrated in the example of , the network entity 205 may scramble the CRC bits included in the grant 240-b using the RA-RNTI determined using the parameter UE_type set to a value of 1. In this example, the UE 215-b may determine that the grant 240-b includes CRC bits scrambled by the RA-RNTI associated with the eRedCap UE. For example, the UE 215-b may determine (e.g., calculate) a CRC value for the grant 240-b based on the UE_type parameter (e.g., index value, identifier) ​​representing the eRedCap UE (e.g., having a value of 1). In this example, the UE 215-b may determine to decode the payload 245-b.

[0112] In some other examples, the wireless communication system 200 may support a random access response scheme in which the network entity 205 may configure multiple (e.g., different) time-frequency resources between multiple (e.g., different) UE types. For example, the network entity 205 may configure multiple (e.g., different) PRACH opportunities between an eRedCap UE (e.g., UE 215-b) and a non-eRedCap UE (e.g., UE 215-a). In such an example, the RA-RNTI for the eRedCap UE and the non-eRedCap UE may be different (e.g., remain different), for example based on one or more calculations (e.g., according to Equation 1). Additionally or alternatively, in such an example, the network entity 205 may avoid transmitting random access responses (e.g., data associated with the random access response) for the eRedCap UE and the non-eRedCap UE in the same payload (e.g., a random access response PDSCH payload). In some examples, the number of PRACH opportunities that can be included in each initial bandwidth portion may be constrained, and therefore, using different PRACH opportunities for multiple (eg, different) UE types may be relatively expensive.

[0113] In some examples, the network entity 205 may configure different initial bandwidth portions for eRedCap UEs and non-eRedCap UEs. Figure 2As illustrated in the example of , UE 215-b may receive a control message 270 from network entity 205, which may indicate one or more initial bandwidth portions to be used for a random access procedure with network entity 205. In such an example, each of the one or more initial bandwidth portions may be associated with a UE type (e.g., a different UE type). In some examples, UE 215-b may determine that an initial bandwidth portion associated with an eRedCap UE is to be used for a random access procedure with network entity 205 (e.g., to send preamble 230-b or one or more other messages). Additionally or alternatively, UE 215-b may determine that none of the initial bandwidth portions included in the control message 270 is associated with an eRedCap UE. In such an example, UE 215-b (e.g., an eRedCap UE) may select one or more of the initial bandwidth portions included in the control message 270 for a random access procedure with network entity 205. For example, UE 215-b may select a single initial bandwidth portion or multiple initial bandwidth portions. In such an example, UE 215-b may send a random access request (e.g., preamble 230-b) to network entity 205 via the selected initial bandwidth portion. That is, UE 215-b may send a random access request (e.g., preamble 230-b) to network entity 205 using the selected single initial bandwidth portion or the selected multiple bandwidth portions.

[0114] In some examples, UE 215-b may select the initial bandwidth portion included in the control message 270 based on one or more rules. For example, UE 215-b may receive an indication of one or more rules for initial bandwidth portion selection from network entity 205. If none of the initial bandwidth portions included in the control message 270 is associated with an eRedCap UE, UE 215-b may receive the indication from network entity 205. Additionally or alternatively, UE 215-b may be configured (e.g., preconfigured) with one or more rules for initial bandwidth portion selection in other ways. In some examples, the one or more rules may include conditional expressions (e.g., if / then statements), or other logical expressions or statements, and other examples of rules that may be used for selection. For example, a rule may define a selection hierarchy. That is, UE 215-b may select an initial bandwidth portion among the one or more initial bandwidth portions according to the selection hierarchy. In some examples, the hierarchy may prioritize the initial bandwidth portion based on the similarity between the eRedCap UE and other UE types that may be associated with the configured initial bandwidth portion. For example, the hierarchy may prioritize an initial bandwidth portion associated with a RedCap UE over other initial bandwidth portions that may be associated with an eMBB UE. In such an example, if an initial bandwidth portion for an eRedCap UE (e.g., a separate initial bandwidth portion) is not configured, UE 215-b may select a bandwidth portion configured for the RedCap UE. That is, if a RedCap initial bandwidth portion is configured (e.g., using control message 270), UE 215-b (e.g., an eRedCap UE) may use the RedCap initial bandwidth portion as the initial bandwidth portion for the eRedCap UE. In some examples, the RedCap initial bandwidth portion may not be configured. In such an example, UE 215-b may select an initial bandwidth portion associated with another UE type, or UE 215-b may select a default initial bandwidth portion (e.g., an NR bandwidth portion). For example, if a RedCap initial bandwidth portion is not configured, UE 215-b may use the default initial bandwidth portion as the initial bandwidth portion for the eRedCap UE. In some examples, selecting the initial bandwidth portion according to one or more rules may enable increased flexibility (eg, and increased resource usage) at network entity 205 , among other possible benefits.

[0115] Figure 3An example of a process flow 300 for supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the process flow 300 may implement one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 300 may include example operations associated with the network entity 305, the UE 315-a, and the UE 315-b, which may be referenced Figure 1 and Figure 2 Examples of corresponding devices described. The operations performed by the network entity 305 and the UE 315 may support improvements to the communication between the UE 315 and the network entity 305 and other benefits. In the following description of the process flow 300, the operations between the UE 315 and the network entity 305 may be performed in an order different from the example order shown in the figure. Additionally or alternatively, the operations performed by the UE 315 and the network entity 305 may be performed in a different order or at a different time. Some operations may also be omitted.

[0116] In some examples, multiple UE types may use the same set of time-frequency resources (e.g., the same random access opportunity) to send random access requests to a network entity as part of a random access procedure for establishing a connection with the network entity. For example, at 320, UE 315-b may use a random access opportunity to send a random access request (e.g., including a random access preamble) to network entity 305. In this example, at 325, UE 315-a may use the same random access opportunity to send another random access request to network entity 305. In response, network entity 305 may send a random access response to UE 315-a and UE 315-b. Figure 3 In the example of , UE 315-a can be an example of a non-eRedCap UE (such as a RedCap UE or an eMBB UE). Additionally or alternatively, UE 315-b can be an example of an eRedCap UE. That is, UE 315-b can be associated with an eRedCap UE type, which can correspond to reduced capabilities relative to a RedCap UE type and an eMBB UE type (e.g., a UE type associated with UE 315-a).

[0117] At 330, the network entity 305 may send a random access response to the UE 315-a and the UE 315-b during the random access window associated with the random access request (e.g., sent at 320 and 325). The random access response may be as described throughout this disclosure (including references to Figure 2) is an example of a random access response described in the context ... In some examples, the first bandwidth processing capability may be related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth used for PDSCH or PUSCH.

[0118] In some examples, the UE type information may include corresponding UE type information for each corresponding UE type in the one or more UE types. In such examples, UE 315-b may receive mapping information that maps each corresponding UE type information in the UE type information to a corresponding UE type in the one or more UE types. Additionally or alternatively, one or more of the corresponding UE type information in the UE type information may correspond to a set of different UE types.

[0119] At 335, in response to receiving the random access response from the network entity 305, the UE 315-b may determine that the random access response is associated with the first UE type. For example, the UE 315-b may 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 as described throughout this disclosure (including reference 1 to FIG. 1 ). Figure 2 ) is an example of a mapping described in . For example, the mapping may include a set of one or more bits in the field representing a set of different UE types. In some examples, the UE 315-b may receive the mapping information from the network entity 305, such as in a system information message or a handover command.

[0120] Additionally or alternatively, UE 315-b may 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 the CRC bits included in the random access response. For example, UE 315-b may determine that the random access response includes a CRC value scrambled by the RA-RNTI associated with the first UE type. In this example, UE315-b may calculate the RA-RNTI value based on an index representing the first UE type according to 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 more indexes representing multiple (e.g., different) UE types. For example, the index value may be one of multiple index values ​​indicated to UE 315-b (or otherwise configured at the UE). In this example, each corresponding index value may be associated with a corresponding UE type (e.g., a corresponding UE type among multiple UE types including the first UE type).

[0121] At 340, UE 315-b may decode the transport block of the random access response based on the first UE type. For example, UE 315-b may decode the transport block based on determining that UE 315-b is the first UE type (or another UE type) and based on that the random access response is associated with the first UE type. That is, UE 315-b may decode the transport block based on that UE 315-b is an eRedCap UE and the random access response is associated with an eRedCap UE.

[0122] Figure 4 An example of a process flow 400 for supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 may implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the process flow 300. For example, the process flow 400 may include example operations associated with a network entity 405 and a UE 415, which may be referenced Figures 1 to 3 Examples of corresponding devices described. The operations performed by the network entity 405 and the UE 415 may support improvements to the communication between the UE 415 and the network entity 405 and other benefits. In the following description of the process flow 400, the operations between the UE 415 and the network entity 405 may be performed in an order different from the example order shown in the figure. Additionally or alternatively, the operations performed by the UE 415 and the network entity 405 may be performed in a different order or at a different time. Some operations may also be omitted. In some other examples, the network entity 405 may configure the UE 415 with multiple (e.g., different) time-frequency resources that may be associated with multiple (e.g., different) UE types.

[0123] At 420, UE 415 may receive a control message from network entity 405. The control message may be as described throughout this disclosure (including references to Figure 2 ) is an example of a control message described in the foregoing. For example, the control message may indicate one or more initial bandwidth parts to be used for random access of the network entity 405. In some examples, each of the one or more initial bandwidth parts may be associated with a corresponding one or more UE types. For example, the one or more initial bandwidth parts may be associated with multiple (e.g., different) UE types.

[0124] At 425, UE 415 may determine that none of the initial bandwidth portions included in the control message received at 420 is associated with the first UE type. Figure 4 In the example of , the first UE type corresponds to an eRedCap UE type. For example, UE 415 may determine that none of the initial bandwidth portions are associated with an eRedCap UE. That is, UE 415 may determine that the eRedCap UE is not associated with the initial bandwidth portion included in (or indicated by) the control message.

[0125] At 430, the UE 415 may select one of the initial bandwidth portions (e.g., a specific initial bandwidth portion, a single initial bandwidth portion) for use in a random access procedure with the network entity 405. In some examples, the UE 415 may select the specific initial bandwidth portion from the one or more initial bandwidth portions included in the control message according to a rule for initial bandwidth portion selection. For example, the UE 415 may select the specific initial bandwidth portion according to the rule for bandwidth portion selection, such as when none of the one or more initial bandwidth portions included in the control message is associated with the first UE type (e.g., an eRedCap UE). The rule may be as described throughout this disclosure (including reference 44 to FIG. 1 ). Figure 2 ). For example, the rule may instruct UE 415 to select a specific initial bandwidth portion among the one or more initial bandwidth portions according to a hierarchy. That is, the rule may define a selection hierarchy. In some examples, the selection hierarchy may prioritize (e.g., rank) initial bandwidth portions associated with RedCap UEs over initial bandwidth portions associated with other UE types (e.g., eMBB UEs). In some examples, UE 415 may select multiple initial bandwidth portions.

[0126] At 435, the UE 415 may send a random access request to the network entity 405 via the selected initial bandwidth portion included in the control message (or via the selected multiple initial bandwidth portions included in the control message). The random access request may be as described throughout this disclosure (including references to Figure 2) as described in the example of a random access request. For example, as part of a random access procedure with the network entity 405, a random access request may be sent from the UE 415.

[0127] Figure 5 A block diagram 500 of a device 505 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0128] Receiver 510 may provide means for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to random access response schemes for eRedCap UEs), such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0129] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to random access response schemes for eRedCap UEs) (such as packets, user data, control information, or any combination thereof). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0130] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the random access response scheme for eRedCap UEs as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0131] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0132] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0133] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0134] The communication manager 520 may support wireless communications at a first network node (e.g., device 505) according to examples as disclosed herein. For example, the communication manager 520 may be configured as or otherwise support components for receiving a random access response from a second network node during a random access window associated with a random access request of the first network node. The communication manager 520 may be configured as or otherwise support components for determining that the random access response is associated with a first UE type. The communication manager 520 may be configured as or otherwise support components for decoding a transport block of the random access response based on the determination and that the first network node is the first UE type.

[0135] Additionally or alternatively, the communication manager 520 may support wireless communication at the first network node (e.g., device 505) according to examples as disclosed herein. For example, the communication manager 520 may be configured as or otherwise support 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 corresponding one or more UE types. The communication manager 520 may be configured as or otherwise support means for determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The communication manager 520 may be configured as or otherwise support means for: selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to a second network node according to a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the ranking is based on a respective UE type associated with each of the one or more PRACH resources. The communication manager 520 may be configured as or otherwise support means for: sending a random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0136] Additionally or alternatively, the communication manager 520 may support wireless communication at the first network node (e.g., device 505) according to examples as disclosed herein. For example, the communication manager 520 may be configured as or otherwise support means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of the second network node, each of the one or more initial bandwidth parts being associated with a corresponding one or more UE types. The communication manager 520 may be configured as or otherwise support means for determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The communication manager 520 may be configured as or otherwise support means for: selecting a specific one of the one or more initial bandwidth parts included in the control message for use in a random access procedure with a second network node according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the ordering is based on a respective UE type associated with each of the one or more initial bandwidth parts. The communication manager 520 may be configured as or otherwise support means for: sending a random access request to the second network node via the selected one of the one or more initial bandwidth parts.

[0137] By including or configuring a communication manager 520 according to examples as described herein, a device 505 (e.g., a processor controlling or otherwise coupled to a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0138] Figure 6 A block diagram 600 of a device 605 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0139] The receiver 610 may provide means for receiving 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). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0140] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to random access response schemes for eRedCap UEs) (such as packets, user data, control information, or any combination thereof). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0141] The device 605 or its various components may be examples of components for performing various aspects of the random access response scheme for eRedCap UEs as described herein. For example, the communication manager 620 may include a window component 625, a UE type component 630, a random access response component 635, a control message component 640, a selection component 645, a random access request component 650, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0142] The communication manager 620 may support wireless communications at a first network node (e.g., device 605) according to examples as disclosed herein. The window component 625 may be configured as or otherwise support means for receiving a random access response from a second network node during a random access window associated with a random access request of the first network node. The UE type component 630 may be configured as or otherwise support means for determining that the random access response is associated with a first UE type. The random access response component 635 may be configured as or otherwise support means for decoding a transport block of the random access response based on the determination and that the first network node is the first UE type.

[0143] Additionally or alternatively, the communication manager 620 may support wireless communication at the first network node (e.g., device 605) according to examples as disclosed herein. The control message component 640 may be configured as or otherwise support means for receiving a control message indicating one or more PRACH resources to be used for random access of the second network node, each of the one or more PRACH resources being associated with a corresponding one or more UE types. The UE type component 630 may be configured as or otherwise support means for determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The selecting component 645 may be configured as or otherwise support means for: selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, wherein the ordering is based on a respective UE type associated with each of the one or more PRACH resources. The random access requesting component 650 may be configured as or otherwise support means for: sending a random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0144] Additionally or alternatively, the communication manager 620 may support wireless communication at the first network node (e.g., device 605) according to examples as disclosed herein. The control message component 640 may be configured as or otherwise support means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of the second network node, each of the one or more initial bandwidth parts being associated with a corresponding one or more UE types. The UE type component 630 may be configured as or otherwise support means for determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The selecting component 645 may be configured as or otherwise support means for: selecting a particular one of the one or more initial bandwidth parts included in the control message for use in a random access procedure with a second network node according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the ordering is based on a respective UE type associated with each of the one or more initial bandwidth parts. The random access requesting component 650 may be configured as or otherwise support means for: sending a random access request to the second network node via the selected one of the one or more initial bandwidth parts.

[0145] Figure 7 A block diagram 700 of a communication manager 720 supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the random access response scheme for an eRedCap UE as described herein. For example, the communication manager 720 may include a window component 725, a UE type component 730, a random access response component 735, a control message component 740, a selection component 745, a random access request component 750, a mapping component 755, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0146] The communication manager 720 may support wireless communications at the first network node according to examples as disclosed herein. The window component 725 may be configured as or otherwise support means for receiving a random access response from the second network node during a random access window associated with a random access request of the first network node. The UE type component 730 may be configured as or otherwise support means for determining that the random access response is associated with a first UE type. The random access response component 735 may be configured as or otherwise support means for decoding a transport block of the random access response based on the determination and that the first network node is the first UE type.

[0147] In some examples, to support determining that a random access response is associated with a first UE type, the random access response component 735 may be configured as or otherwise support a component for determining that the random access response includes a downlink control channel message, the downlink control channel message including UE type information indicating one or more UE types associated with the downlink control channel message, wherein the one or more UE types include the first UE type.

[0148] In some examples, the UE type information includes corresponding UE type information for each corresponding UE type in the one or more UE types, and the mapping component 755 may be configured as or otherwise support a component for receiving mapping information that maps each corresponding UE type information in the UE type information to a corresponding UE type in the one or more UE types.

[0149] In some examples, to support receiving mapping information, mapping component 755 may be configured as or otherwise support means for: receiving a system information message or a handover command, wherein the system information message or the handover command includes mapping information. In some examples, at least one of the corresponding UE type information in the UE type information corresponds to a set of different UE types.

[0150] In some examples, to support receiving a random access response from a second network node during a random access window, the window component 725 may be configured as or otherwise support means for receiving the random access response after receiving one or more other random access responses during the random access window.

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

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

[0153] In some examples, to support determining that a random access response is associated with a first UE type, the UE type component 730 may be configured as or otherwise support a component for determining that the random access response includes a downlink control channel message, the downlink control channel message including UE type information included in an MCS level field or a transport block scaling field, the UE type information indicating a first UE type.

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

[0155] In some examples, the index value is an index value in a set of multiple index values. In some examples, each corresponding index value in the set of multiple index values ​​is associated with a corresponding UE type in a set of multiple UE types. In some examples, the set of multiple UE types includes a first UE type. In some examples, the index value is not zero. In some examples, the random access request component 750 can be configured as or otherwise support a component for the following operations: sending an indication that the first network node included in the random access request belongs to the first UE type.

[0156] In some examples, the eRedCap UE type corresponds to reduced capabilities relative to the RedCap UE type and the 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 the eMBB UE. In some examples, the first maximum bandwidth processing capability is related to one or more combinations of: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0157] Additionally or alternatively, the communication manager 720 may support wireless communication at the first network node according to examples as disclosed herein. The control message component 740 may be configured as or otherwise support 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 corresponding one or more UE types. In some examples, the UE type component 730 may be configured as or otherwise support means for determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The selecting component 745 may be configured as or otherwise support means for: selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the ranking is based on a respective UE type associated with each of the one or more PRACH resources. The random access requesting component 750 may be configured as or otherwise support means for: sending a random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources.

[0158] In some examples, when none of the one or more PRACH resources included in the control message is associated with the first UE type, the ranking prioritizes PRACH resources associated with the second UE type. In some examples, when none of the one or more PRACH resources included in the control message is associated with the first UE type and none of the one or more PRACH resources included in the control message is associated with the second UE type, the ranking prioritizes PRACH resources by default. In some examples, when none of the one or more PRACH resources included in the control message is associated with the first UE type and none of the one or more PRACH resources included in the control message is associated with the second UE type, the ranking prioritizes PRACH resources associated with the third UE type.

[0159] 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 relative to the RedCap UE type and the 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 the eMBB UE. In some examples, the first maximum bandwidth processing capability is related to one or more combinations of: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0160] In some examples, control message component 740 may be configured as or otherwise support means for receiving a second control message indicating an ordering for PRACH resource selection.

[0161] Additionally or alternatively, the communication manager 720 may support wireless communication at the first network node according to examples as disclosed herein. The control message component 740 may be configured as or otherwise support means for receiving a control message indicating one or more initial bandwidth parts to be used for random access of the second network node, each of the one or more initial bandwidth parts being associated with one or more corresponding UE types. In some examples, the UE type component 730 may be configured as or otherwise support means for determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The selection component 745 may be configured as or otherwise support means for selecting a specific 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 according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ordering is based on the corresponding UE type associated with each of the one or more initial bandwidth parts. Random access request component 750 may be configured as or otherwise support means for sending a random access request to a second network node via a selected initial bandwidth portion of the one or more initial bandwidth portions.

[0162] In some examples, when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, the ordering prioritizes the initial bandwidth parts associated with the second UE type. In some examples, when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the ordering prioritizes the initial bandwidth parts by default. In some examples, when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the ordering prioritizes the initial bandwidth parts associated with the third UE type.

[0163] 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 relative to the RedCap UE type and the 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 the eMBB UE. In some examples, the first maximum bandwidth processing capability is related to one or more combinations of: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0164] In some examples, control message component 740 may be configured as or otherwise support means for receiving a second control message indicating an ordering for initial bandwidth portion selection.

[0165] Figure 8 A diagram of a system 800 including a device 805 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0166] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0167] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired or wireless link, as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

[0168] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 830 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0169] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) so that the device 805 performs various functions (e.g., various functions or tasks supporting a random access response scheme for an eRedCapUE). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0170] The communication manager 820 may support wireless communications at a first network node (e.g., device 805) according to examples as disclosed herein. For example, the communication manager 820 may be configured as or otherwise support components for receiving a random access response from a second network node during a random access window associated with a random access request of the first network node. The communication manager 820 may be configured as or otherwise support components for determining that the random access response is associated with a first UE type. The communication manager 820 may be configured as or otherwise support components for decoding a transport block of the random access response based on the determination and that the first network node is the first UE type.

[0171] Additionally or alternatively, the communication manager 820 may support wireless communication at a first network node (e.g., device 805) according to examples as disclosed herein. For example, the communication manager 820 may be configured as or otherwise support a component 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 corresponding one or more UE types. The communication manager 820 may be configured as or otherwise support a component for: determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The communication manager 820 may be configured as or otherwise support a component for: selecting a specific 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 according to a rule for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type. The communications manager 820 may be configured as or otherwise support means for sending a random access request to the second network node via a selected initial bandwidth portion of the one or more initial bandwidth portions.

[0172] By including or configuring a communication manager 820 according to examples as described herein, the device 805 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

[0173] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include various aspects that can be executed by the processor 840 to cause the device 805 to perform a random access response scheme for an eRedCap UE as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0174] Fig. 9A block diagram 900 of a device 905 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0175] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0176] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0177] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the random access response scheme for eRedCap UEs as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0178] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0179] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0180] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0181] The communication manager 920 may support wireless communication at a first network node (e.g., device 905) according to examples as disclosed herein. For example, the communication manager 920 may be configured as or otherwise support components for the following operations: receiving a random access request from a second network node. The communication manager 920 may be configured as or otherwise support components for the following operations: determining that the second network node is associated with a first UE type. The communication manager 920 may be configured as or otherwise support components for the following operations: in response to the random access request, sending a random access response based on the second network node being associated with the first UE type, the random access response indicating that the random access response is for a UE belonging to the first UE type.

[0182] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled to a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0183] Fig.10 A block diagram 1000 of a device 1005 supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0184] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0185] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0186] The device 1005 or its various components may be examples of components for performing various aspects of the random access response scheme for eRedCap UEs as described herein. For example, the communication manager 1020 may include a request component 1025, a UE type determination component 1030, a random access component 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0187] The communication manager 1020 may support wireless communications at a first network node (e.g., device 1005) according to examples as disclosed herein. The request component 1025 may be configured as or otherwise support means for receiving a random access request from a second network node. The UE type determination component 1030 may be configured as or otherwise support means for determining that the second network node is associated with a first UE type. The random access component 1035 may be configured as or otherwise support means for: in response to the random access request, sending a random access response based on the second network node being associated with the first UE type, the random access response indicating that the random access response is for a UE belonging to the first UE type.

[0188] Fig.11A block diagram 1100 of a communication manager 1120 supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the random access response scheme for an eRedCap UE as described herein. For example, the communication manager 1120 may include a request component 1125, a UE type determination component 1130, a random access component 1135, a UE type information component 1140, a CRC component 1145, a mapping information component 1150, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0189] The communication manager 1120 may support wireless communications at the first network node according to examples as disclosed herein. The request component 1125 may be configured as or otherwise support means for receiving a random access request from the second network node. The UE type determination component 1130 may be configured as or otherwise support means for determining that the second network node is associated with the first UE type. The random access component 1135 may be configured as or otherwise support means for: in response to the random access request, sending a random access response based on the second network node being associated with the first UE type, the random access response indicating that the random access response is for a UE belonging to the first UE type.

[0190] In some examples, the random access component 1135 may be configured as or otherwise support a component for: including, as part of a random access response, a downlink control channel message that includes UE type information indicating one or more UE types associated with the downlink control channel message, wherein the one or more UE types include a first UE type.

[0191] In some examples, the UE type information includes corresponding UE type information for each corresponding UE type in the one or more UE types, and the mapping information component 1150 may be configured as or otherwise support a component for sending mapping information that maps each corresponding UE type information in the UE type information to a corresponding UE type in the one or more UE types.

[0192] In some examples, to support sending mapping information, mapping information component 1150 may be configured as or otherwise support a component for: sending a system information message or a handover command, wherein the system information message or the handover command includes mapping information. In some examples, at least one of the corresponding UE type information in the UE type information corresponds to a group of different UE types.

[0193] In some examples, to support sending a random access response, the random access component 1135 may be configured as or otherwise support means for sending the random access response during a random access window after sending one or more other random access responses during the random access window.

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

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

[0196] In some examples, UE type information component 1140 may be configured as or otherwise support a component for: including, as part of a random access response, a downlink control channel message that includes UE type information included in an MCS level field or a transport block scaling field, the UE type information indicating a first UE type.

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

[0198] In some examples, the index value is an index value in a set of multiple index values. In some examples, each corresponding index value in the set of multiple index values ​​is associated with a corresponding UE type in 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 not zero.

[0199] In some examples, to support determining that the second network node is associated with the first UE type, request component 1125 may be configured as or otherwise support means for receiving an indication included in the random access request that the second network node belongs to the first UE type.

[0200] In some examples, the first UE type is an eRedCap UE type corresponding to reduced capabilities relative to the RedCap UE type and the 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 the eMBB UE. In some examples, the first maximum bandwidth processing capability is related to one or more combinations of: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0201] Fig.12 A diagram of a system 1200 including a device 1205 supporting a random access response scheme for an eRedCap UE in accordance with one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0202] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which may be operable to perform or support operations based on received or obtained information or signals, or may be operable to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0203] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1225 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0204] The processor 1235 may 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, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) so that the device 1205 performs various functions (e.g., various functions or tasks supporting a random access response scheme for an eRedCapUE). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, the processor 1235 and the memory 1225 being configured to perform the various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing the functions of the device 1205 (e.g., by executing the code 1230). The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (e.g., within the memory 1225). In some specific implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to, for example, other systems or components of the device 1205). For example, the processing system of the device 1205 may refer to a system including various other components or subcomponents of the device 1205 (e.g., the processor 1235, or the transceiver 1210, or the communication manager 1220, or other components or combinations of components of the device 1205). The processing system of device 1205 may interface with other components of device 1205, and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. 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 the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1205 can send information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1205 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0205] In some examples, bus 1240 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1205, or communications performed between different components of device 1205 that may be co-located or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

[0206] In some examples, communication manager 1220 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1220 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0207] The communication manager 1220 may support wireless communications at a first network node (e.g., device 1205) according to examples as disclosed herein. For example, the communication manager 1220 may be configured as or otherwise support components for receiving a random access request from a second network node. The communication manager 1220 may be configured as or otherwise support components for determining that the second network node is associated with a first UE type. The communication manager 1220 may be configured as or otherwise support components for: in response to the random access request, sending a random access response based on the second network node being associated with the first UE type, the random access response indicating that the random access response is for a UE belonging to the first UE type.

[0208] By including or configuring a communications manager 1220 according to examples as described herein, the device 1205 can support techniques for improving communications reliability, reducing latency, more efficiently utilizing communications resources, and improving coordination between devices.

[0209] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include various aspects that can be executed by the processor 1235 to cause the device 1205 to perform a random access response scheme for an eRedCap UE as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0210] Fig.13 A flow chart illustrating a method 1300 for supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be used to perform. In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions. Fig.13 In the example of , the UE is referred to as the first network node.

[0211] At 1305, the method may include receiving a random access response from the second network node during a random access window associated with the random access request of the first network node. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described window component 725 is executed.

[0212] At 1310, the method may include determining that the random access response is associated with the first UE type. The operations of 1310 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference Figure 7 The described UE type component 730 is performed.

[0213] At 1315, the method may include: decoding a transport block of the random access response based on the determination and that the first network node is a first UE type. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference Figure 7 The random access response component 735 described above is performed.

[0214] Fig.14 A flow chart illustrating a method 1400 for supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be used to perform. In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions. Fig.14 In the example of , the UE is referred to as the first network node.

[0215] At 1405, the method may include: receiving a control message indicating one or more PRACH resources to be used for random access of the second network node, each of the one or more PRACH resources being associated with a corresponding one or more UE types. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The control message component 740 described is executed.

[0216] At 1410, the method may include determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figure 7 The described UE type component 730 is performed.

[0217] At 1415, the method may include: selecting a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to an ordering for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, wherein the ordering is based on a respective UE type associated with each of the one or more PRACH resources. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The described selection component 745 is executed.

[0218] At 1420, the method may include sending a random access preamble to the second network node via the selected PRACH resource of the one or more PRACH resources. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The random access request component 750 described above is performed.

[0219] Fig.15 A flow chart illustrating a method 1500 for supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be used to perform. In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions. Fig.15 In the example of , the UE is referred to as the first network node.

[0220] At 1505, the method may include receiving a control message indicating one or more initial bandwidth parts to be used for random access of the second network node, each of the one or more initial bandwidth parts being associated with a corresponding one or more UE types. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 7 The described control message component 740 is executed.

[0221] At 1510, the method may include determining that none of the one or more initial bandwidth portions included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference Figure 7 The described UE type component 730 is performed.

[0222] At 1515, the method may include: selecting a specific initial bandwidth portion of the one or more initial bandwidth portions included in the control message for use in a random access procedure with a second network node according to an ordering for initial bandwidth portion selection when none of the one or more initial bandwidth portions included in the control message is associated with a first UE type, wherein the ordering is based on a respective UE type associated with each of the one or more initial bandwidth portions. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figure 7 The described selection component 745 is executed.

[0223] At 1520, the method may include sending a random access request to the second network node via the selected initial bandwidth portion of the one or more initial bandwidth portions. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 7 The random access request component 750 described above is performed.

[0224] Fig.16 A flow chart illustrating a method 1600 for supporting a random access response scheme for an eRedCap UE according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 as well as Figures 9 to 12 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0225] At 1605, the method may include: receiving a random access request from a second network node. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference Fig.11 The described request component 1125 is executed.

[0226] At 1610, the method may include determining that the second network node is associated with the first UE type. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference Fig.11 The described UE type determination component 1130 is performed.

[0227] At 1615, the method may include: in response to the random access request, sending a random access response based on the second network node being associated with the first UE type, the random access response indicating that the random access response is for a UE belonging to the first UE type. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The described random access component 1135 is performed.

[0228] The following provides an overview of various aspects of the disclosure:

[0229] Aspect 1: A method of wireless communication performed by a first network node, the method 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 corresponding 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 belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; selecting a specific PRACH resource among the one or more PRACH resources included in the control message for sending a random access preamble to the second network node according to 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, wherein the ranking is based on the corresponding UE type associated with each of the one or more PRACH resources; and sending the random access preamble to the second network node via the selected PRACH resource among the one or more PRACH resources.

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

[0231] Aspect 3: A first network node according to Aspect 2, wherein when the one or more PRACH resources included in the control message are not associated with the first UE type and the one or more PRACH resources included in the control message are not associated with the second UE type, the sorting will default to PRACH resource priority.

[0232] Aspect 4: A first network node according to Aspect 2, wherein when none of the one or more PRACH resources included in the control message is associated with the first UE type and none of the one or more PRACH resources included in the control message is associated with the second UE type, the sorting prioritizes PRACH resources associated with a third UE type.

[0233] Aspect 5: The first network node according to aspect 4, wherein the second UE type is a RedCap UE type, and the third UE type is an eMBB UE type.

[0234] Aspect 6: The first network node according to any one of aspects 1 to 5, wherein the eRedCap UE type corresponds to reduced capabilities relative to the RedCap UE type and the eMBB UE type.

[0235] Aspect 7: The first network node according to any one of aspects 1 to 6, wherein the first UE type is associated with a first maximum bandwidth handling capability, the first maximum bandwidth handling capability being lower than a second maximum bandwidth handling capability associated with an eMBB UE.

[0236] Aspect 8: The first network node according to aspect 7, wherein the first maximum bandwidth processing capability is related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0237] Aspect 9: According to the method according to any one of aspects 1 to 8, the method further includes: receiving a second control message indicating the ranking for the PRACH resource selection.

[0238] Aspect 10: A method of wireless communication performed by a first network node, the method 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 corresponding one or more UE types; determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an eRedCap UE type; selecting a specific initial bandwidth part of the one or more initial bandwidth parts included in the control message for use in a random access process with the second network node according to a ranking for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, wherein the ranking is based on the corresponding UE type associated with each of the one or more initial bandwidth parts; and sending a random access request to the second network node via the selected initial bandwidth part of the one or more initial bandwidth parts.

[0239] Aspect 11: The first network node according to aspect 10, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, the ordering prioritizes the initial bandwidth part associated with the second UE type.

[0240] Aspect 12: A first network node according to Aspect 11, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the sorting will default to initial bandwidth part priority.

[0241] Aspect 13: A first network node according to claim 11, wherein when the one or more initial bandwidth parts included in the control message are not associated with the first UE type and the one or more initial bandwidth parts included in the control message are not associated with the second UE type, the sorting prioritizes the initial bandwidth part associated with the third UE type.

[0242] Aspect 14: The first network node according to aspect 13, wherein the second UE type is a RedCap UE type and the third UE type is an eMBB UE type.

[0243] Aspect 15: The first network node according to any one of aspects 10 to 14, wherein the eRedCap UE type corresponds to reduced capabilities relative to the RedCap UE type and the eMBB UE type.

[0244] Aspect 16: The first network node according to any one of aspects 10 to 15, wherein the first UE type is associated with a first maximum bandwidth handling capability, the first maximum bandwidth handling capability being lower than a second maximum bandwidth handling capability associated with an eMBB UE.

[0245] Aspect 17: The first network node according to aspect 16, wherein the first maximum bandwidth processing capability is related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth for PDSCH or PUSCH.

[0246] Aspect 18: The method according to any one of aspects 10 to 17, further comprising: receiving a second control message indicating the ranking for the initial bandwidth portion selection.

[0247] Aspect 19: A first network node, comprising a processing system, wherein the processing system is configured to perform the method according to any one of aspects 1 to 9.

[0248] Aspect 20: A first network node, comprising at least one component for performing the method according to any one of aspects 1 to 9.

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

[0250] Aspect 22: A first network node, the first network node comprising a processing system configured to perform the method according to any one of aspects 10 to 18.

[0251] Aspect 23: A first network node, the first network node comprising at least one component for performing the method according to any one of aspects 10 to 18.

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

[0253] The methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0254] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0255] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0256] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0257] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0258] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, a server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0259] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to the listed alternatives. For example, references to "X is based on A or B" should be interpreted as including within its scope X based on A, X based on B, and X based on A and B. In this regard, references to "X is based on A or B" refer to "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, references to "X is based on A, B, or C" should be interpreted as including within its scope X based on A, X based on B, X based on C, X based on A and B, X based on A and C, X based on B and C, and X based on A, B, and C. In this regard, references to "X is based on A, B, or C" refer to "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based on at least A" unless specifically stated differently. Likewise, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one."

[0260] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0261] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0262] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The terms "aspect" or "example" used herein mean "used as an aspect, example, instance, or illustration," rather than "preferred" or "advantageous over other aspects." The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0263] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, the first network node comprising a processing system, the processing system being configured to: 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 user equipment (UE) types; determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an enhanced reduced capability UE type; selecting, according to a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node, wherein the ranking is based on a respective UE type associated with each of the one or more PRACH resources; and The random access preamble is sent to the second network node via a selected PRACH resource of the one or more PRACH resources.

2. The first network node of claim 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 is associated with the first UE type.

3. The first network node according to claim 2, wherein when the one or more PRACH resources included in the control message are not associated with the first UE type and the one or more PRACH resources included in the control message are not associated with the second UE type, the sorting will default to PRACH resource priority.

4. The first network node of claim 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 is associated with the first UE type and none of the one or more PRACH resources included in the control message is associated with the second UE type.

5. The first network node according to claim 4, wherein: The second UE type is a reduced capability UE type, and The third UE type is an enhanced mobile broadband (eMBB) UE type.

6. The first network node of claim 1, wherein the enhanced reduced capability UE type corresponds to reduced capabilities relative to a reduced capability UE type and an enhanced mobile broadband (eMBB) UE type.

7. The first network node of claim 1, wherein the first UE type is associated with a first maximum bandwidth handling capability that is lower than a second maximum bandwidth handling capability associated with an enhanced mobile broadband (eMBB) UE.

8. The first network node according to claim 7, wherein the first maximum bandwidth handling capability is related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH).

9. The first network node of claim 1 , wherein the processing system is configured to: A second control message is received indicating the ranking for the PRACH resource selection.

10. A first network node for wireless communication, the first network node comprising a processing system, the processing system being configured to: 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 user equipment (UE) types; determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an enhanced reduced capability UE type; selecting, according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, a specific 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 ordering is based on a respective UE type associated with each of the one or more initial bandwidth parts; and A random access request is sent to the second network node via the selected initial bandwidth portion of the one or more initial bandwidth portions.

11. The first network node of claim 10, wherein the ordering 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 is associated with the first UE type.

12. The first network node according to claim 11, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the sorting will default to initial bandwidth part priority.

13. The first network node according to claim 11, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the sorting prioritizes the initial bandwidth part associated with the third UE type.

14. The first network node according to claim 13, wherein: The second UE type is a reduced capability UE type, and The third UE type is an enhanced mobile broadband (eMBB) UE type.

15. The first network node of claim 10, wherein the enhanced reduced capability UE type corresponds to reduced capabilities relative to a reduced capability UE type and an enhanced mobile broadband (eMBB) UE type.

16. The first network node of claim 10, wherein the first UE type is associated with a first maximum bandwidth handling capability that is lower than a second maximum bandwidth handling capability associated with an enhanced mobile broadband (eMBB) UE.

17. The first network node according to claim 16, wherein the first maximum bandwidth handling capability is related to one or more combinations of the following items: radio frequency bandwidth, baseband bandwidth, or bandwidth for physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

18. The first network node of claim 10, wherein the processing system is configured to: A second control message is received indicating the ranking for the initial bandwidth portion selection.

19. A method of wireless communication performed by a first network node, the method comprising: 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 user equipment (UE) types; determining that none of the one or more PRACH resources included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an enhanced reduced capability UE type; selecting, according to a ranking for PRACH resource selection when none of the one or more PRACH resources included in the control message is associated with the first UE type, a specific PRACH resource of the one or more PRACH resources included in the control message for sending a random access preamble to the second network node, wherein the ranking is based on a respective UE type associated with each of the one or more PRACH resources; as well as The random access preamble is sent to the second network node via a selected PRACH resource of the one or more PRACH resources.

20. The first network node of claim 19, wherein the ordering prioritizes PRACH resources associated with a second UE type when none of the one or more PRACH resources included in the control message is associated with the first UE type.

21. The first network node according to claim 20, wherein when the one or more PRACH resources included in the control message are not associated with the first UE type and the one or more PRACH resources included in the control message are not associated with the second UE type, the sorting will default to PRACH resource priority.

22. The first network node of claim 20, 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 is associated with the first UE type and none of the one or more PRACH resources included in the control message is associated with the second UE type.

23. The first network node according to claim 22, wherein: The second UE type is a reduced capability UE type, and The third UE type is an enhanced mobile broadband (eMBB) UE type.

24. The first network node of claim 19, wherein the enhanced reduced capability UE type corresponds to reduced capabilities relative to a reduced capability UE type and an enhanced mobile broadband (eMBB) UE type.

25. A method of wireless communication performed by a first network node, the method 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 user equipment (UE) types; determining that none of the one or more initial bandwidth parts included in the control message is associated with a first UE type, wherein the first network node belongs to the first UE type, and wherein the first UE type is an enhanced reduced capability UE type; selecting, according to an ordering for initial bandwidth part selection when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type, a specific 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 ordering is based on a respective UE type associated with each of the one or more initial bandwidth parts; as well as A random access request is sent to the second network node via the selected initial bandwidth portion of the one or more initial bandwidth portions.

26. The first network node of claim 25, wherein the ordering 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 is associated with the first UE type.

27. The first network node according to claim 26, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the sorting will default to initial bandwidth part priority.

28. A first network node according to claim 26, wherein when none of the one or more initial bandwidth parts included in the control message is associated with the first UE type and none of the one or more initial bandwidth parts included in the control message is associated with the second UE type, the sorting prioritizes the initial bandwidth part associated with the third UE type.

29. The first network node according to claim 28, wherein: The second UE type is a reduced capability UE type, and The third UE type is an enhanced mobile broadband (eMBB) UE type.

30. The first network node of claim 25, wherein the enhanced reduced capability UE type corresponds to reduced capabilities relative to a reduced capability UE type and an enhanced mobile broadband (eMBB) UE type.

Images