# US 2026/0281927 A1 · Enhanced reduced capability system information and control resource set

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0281927 A1
- Document ID: US20260281927A1
- Status: Published application
- Kind: A1
- Application number: 18/873,900
- Filed: 2022-08-31
- Published: 2026-09-17
- Earliest claimed: 2022-08-31
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Ruiming ZHENG; Linhai HE; Jing LEI
- Web page: https://patentgrep.com/patent/US20260281927A1

## CPC

- H04W 48/12: using downlink control channel
- H04W 56/002: {Mutual synchronization}
- H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH}
- H04W 74/0833: Random access procedures, e.g. with 4-step access
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, from a network node, a synchronization signal block (SSB) indicating an enhanced reduced capability (eRedCap) specific control resource set (CORESET) that is separate from another CORESET indicated by the SSB. The UE may receive, from the network node, the eRedCap-specific system information from the eRedCap-specific CORESET. Numerous other aspects are described.

## Claims

### Claim 1

A user equipment (UE) for wireless communication, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
receive, from a network node, a synchronization signal block (SSB) indicating an enhanced reduced capability (eRedCap)-specific control resource set (CORESET) that is separate from another CORESET indicated by the SSB; and
receive, from the network node, eRedCap-specific system information from the eRedCap-specific CORESET.

### Claim 2 (depends on 1)

The UE of claim 1, wherein the eRedCap-specific system information is included in eRedCap-specific system information blocks (SIBs).

### Claim 3 (depends on 1)

The UE of claim 1, wherein the eRedCap-specific system information is included in system information blocks (SIBs) that are not eRedCap-specific.

### Claim 4 (depends on 3)

The UE of claim 3, wherein the SIBs include at least one eRedCap-specific parameter.

### Claim 5 (depends on 1)

The UE of claim 1, wherein the eRedCap-specific system information indicates an eRedCap-specific resource that includes at least one of:
an eRedCap-specific initial downlink bandwidth part,
an eRedCap-specific initial uplink bandwidth part, or
an eRedCap-specific common search space for the eRedCap-specific system information, paging, and random access communications.

### Claim 6 (depends on 1)

The UE of claim 1, wherein the one or more processors are further configured to:
perform a random access channel (RACH) procedure using an eRedCap-specific initial downlink bandwidth part; and
monitor one or more paging occasions in the eRedCap-specific CORESET, in the eRedCap-specific initial downlink bandwidth part, while performing the RACH procedure.

### Claim 7 (depends on 1)

The UE of claim 1, wherein the SSB includes a system information parameter that maps to the eRedCap-specific CORESET.

### Claim 8 (depends on 1)

The UE of claim 1, wherein the SSB is configured to be an eRedCap-specific SSB, and wherein the eRedCap-specific CORESET is associated with a frequency domain offset.

### Claim 9 (depends on 1)

The UE of claim 1, wherein the eRedCap-specific system information is associated with an eRedCap-specific system information radio network temporary identifier.

### Claim 10 (depends on 1)

The UE of claim 1, wherein the one or more processors, to receive the eRedCap-specific system information from the eRedCap-specific CORESET, are configured to:
perform radio frequency retuning, based at least in part on the SSB, to receive the eRedCap-specific system information from the eRedCap-specific CORESET.

### Claim 11 (depends on 1)

The UE of claim 1, wherein the eRedCap-specific system information is received using a first bandwidth part; and
wherein the one or more processors are further configured to:
communicate with the network node using a second bandwidth part that is separate from the first bandwidth part.

### Claim 12 (depends on 11)

The UE of claim 11, wherein the one or more processors, to communicate with the network node using the second bandwidth part, are configured to:
perform a random access channel (RACH) procedure using the second bandwidth part.

### Claim 13 (depends on 12)

The UE of claim 12, wherein performing the RACH procedure using the second bandwidth part is based at least in part on a width of a non-eRedCap-specific initial uplink bandwidth part and a capability of the UE.

### Claim 14 (depends on 12)

The UE of claim 12, wherein separate RACH occasion resources are configured in separate eRedCap-specific initial uplink bandwidth parts.

### Claim 15 (depends on 11)

The UE of claim 11, wherein the eRedCap-specific system information and a communication using the second bandwidth part are time domain duplexed, and a first center frequency of the first bandwidth part is different from a second center frequency of the second bandwidth part.

### Claim 16 (depends on 15)

The UE of claim 15, wherein the one or more processors, to communicate with the network node using the second bandwidth part, are configured to:
perform a random access channel (RACH) procedure using the second bandwidth part and based at least in part on an eRedCap-specific configured radio frequency retune gap,
wherein separate RACH occasion resources are configured in separate eRedCap-specific initial uplink bandwidth parts.

### Claim 17 (depends on 11)

The UE of claim 11, wherein the first bandwidth part and the second bandwidth part are separately configured via at least one of:
radio resource control (RRC) configuration, or
the eRedCap-specific system information.

### Claim 18 (depends on 17)

The UE of claim 17, wherein the first bandwidth part is an initial downlink bandwidth part, and the second bandwidth part is an initial uplink bandwidth part.

### Claim 19 (depends on 17)

The UE of claim 17, wherein the one or more processors, to separate configurations for the first bandwidth part and the second bandwidth part may, are configured to:
a time division duplex configuration, or
a frequency division duplex configuration.

### Claim 20 (depends on 1)

The UE of claim 1, wherein the UE is an eRedCap UE.

### Claim 21 (depends on 1)

The UE of claim 1, wherein the SSB is a cell-defining SSB.

### Claim 22

A network node for wireless communication, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
transmit a synchronization signal block (SSB) indicating an enhanced reduced capability (eRedCap)-specific control resource set (CORESET) that is separate from another CORESET indicated by the SSB; and
transmit eRedCap-specific system information using the eRedCap-specific CORESET.

### Claim 23 (depends on 22)

The network node of claim 22, wherein the eRedCap-specific system information is included in eRedCap-specific system information blocks (SIBs).

### Claim 24 (depends on 22)

The network node of claim 22, wherein the eRedCap-specific system information is included in system information blocks (SIBs) that are not eRedCap-specific.

### Claim 25 (depends on 24)

The network node of claim 24, wherein the SIBs include at least one eRedCap-specific parameter.

### Claim 26 (depends on 22)

The network node of claim 22, wherein the eRedCap-specific system information indicates an eRedCap-specific resource that includes at least one of:
an eRedCap-specific initial downlink bandwidth part,
an eRedCap-specific initial uplink bandwidth part, or
an eRedCap-specific common search space for the eRedCap-specific system information, paging, and random access communications.

### Claim 27 (depends on 22)

The network node of claim 22, wherein the one or more processors are further configured to:
perform a random access channel (RACH) procedure using an eRedCap-specific initial downlink bandwidth part.

### Claim 28 (depends on 22)

The network node of claim 22, wherein the SSB includes a system information parameter that maps to the eRedCap-specific CORESET.

### Claim 29

A method of wireless communication performed by an apparatus of a user equipment (UE), comprising:
receiving, from a network node, a synchronization signal block (SSB) indicating an enhanced reduced capability (eRedCap)-specific control resource set (CORESET) that is separate from another CORESET indicated by the SSB; and
receiving, from the network node, eRedCap-specific system information from the eRedCap-specific CORESET.

### Claim 30

A method of wireless communication performed by a network node, comprising:
transmitting a synchronization signal block (SSB) indicating an enhanced reduced capability (eRedCap)-specific control resource set (CORESET) that is separate from another CORESET indicated by the SSB; and
transmitting eRedCap-specific system information using the eRedCap-specific CORESET.
