# US 2023/0276227 A1 · Method and device for providing terminal capability information in wireless communication system

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

- Number: US 2023/0276227 A1
- Document ID: US20230276227A1
- Status: Published application
- Kind: A1
- Application number: 18/014,456
- Filed: 2021-06-22
- Published: 2023-08-31
- Earliest claimed: 2020-07-07
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Seungri JIN; Soenghun KIM
- Web page: https://patentgrep.com/patent/US20230276227A1

## CPC

- H04W 8/24: Transfer of terminal data
- H04W 76/10: Connection setup
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 76/28: Discontinuous transmission [DTX]; Discontinuous reception [DRX]
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

The disclosure provides a method of reporting user equipment (UE) capability information by a UE, the method including receiving, from a base station (BS), system information including an indicator supporting a type 2 UE; performing camp-on for a serving cell corresponding to the BS based on the system information; performing a radio resource control (RRC) connection establishment procedure with the BS; transmitting, to the BS, an RRCSetupRequest message including type 1 capability information of the UE; receiving an RRCSetup message from the BS; transmitting, to the BS, type 3 UE capability information of the UE in an RRCSetupComplete message in response to the RRCSetup message; receiving a UE capability enquiry message from the BS; and transmitting at least one of the type 1 capability information, type 2 capability information and type 3 capability information of the UE to the BS in response to the UE capability enquiry message.

## Claims

### Claim at position 1

1-15. (canceled)

### Claim 16

A method performed by a user equipment (UE), the method comprising:
receiving, from a base station (BS), system information including an indicator indicating whether a reduced capability (RedCap) UE is supported on a cell;
in case that the RedCap UE is supported on the cell, transmitting a msg1 including a random access (RA) preamble to the BS, based on preamble configuration information included in the system information; and
based on a msg2 received as a response for the RA preamble, transmitting, to the BS, a msg3 including a logical channel identifier (LCD) indicating that the UE is the RedCap UE.

### Claim 17 (depends on 16)

The method of claim 16,
wherein in case that the msg3 is a RRCSetupRequest message, a size of the RRCSetupRequest message including the LCID is M bits, and
wherein in case that the msg3 is a RRCResumeRequest message, a size of the RRCResumeRequest message including the LCID is M bits or N bits.

### Claim 18 (depends on 16)

The method of claim 16, further comprising:
receiving a UE capability enquiry message from the BS; and
transmitting, to the BS, a UE capability information message including RedCap UE capability information.

### Claim 19 (depends on 16)

The method of claim 16, further comprising:
in case that a msg4 is received as a response for the msg3, transmitting a RRCSetupComplete message to the BS,
wherein the RRCSetupComplete message comprises non access stratum (NAS) container including registration request message to a core network (CN).

### Claim 20

A method performed by a base station (BS), the method comprising:
transmitting, to a user equipment (UE), system information including an indicator indicating whether a reduced capability (RedCap) UE is supported on a cell;
in case that the RedCap UE is supported on the cell, receiving a msg1 including a random access (RA) preamble from the UE, based on preamble configuration information included in the system information; and
based on a msg2 transmitted as a response for the RA preamble, receiving, from the UE, a msg3 including a logical channel identifier (LCD) indicating that the UE is the RedCap UE.

### Claim 21 (depends on 20)

The method of claim 20,
wherein in case that the msg3 is a RRCSetupRequest message, a size of the RRCSetupRequest message including the LCID is M bits, and
wherein in case that the msg3 is a RRCResumeRequest message, a size of the RRCResumeRequest message including the LCID is M bits or N bits.

### Claim 22 (depends on 20)

The method of claim 20, further comprising:
transmitting a UE capability enquiry message to the UE; and
receiving, from the UE, a UE capability information message including RedCap UE capability information.

### Claim 23 (depends on 20)

The method of claim 20, further comprising:
in case that a msg4 is transmitted as a response for the msg3, receiving a RRCSetupComplete message from the UE,
wherein the RRCSetupComplete message comprises non access stratum (NAS) container including registration request message to a core network (CN).

### Claim 24

A user equipment (UE) comprising:
a transceiver; and
at least one processor coupled with the transceiver and configured to:
receive, from a base station (BS), system information including an indicator indicating whether a reduced capability (RedCap) UE is supported on a cell,
in case that the RedCap UE is supported on the cell, transmit a msg1 including a random access (RA) preamble to the BS, based on preamble configuration information included in the system information, and
based on a msg2 received as a response for the RA preamble, transmit, to the BS, a msg3 including a logical channel identifier (LCD) indicating that the UE is the RedCap UE.

### Claim 25 (depends on 24)

The UE of claim 24,
wherein in case that the msg3 is a RRCSetupRequest message, a size of the RRCSetupRequest message including the LCID is M bits, and
wherein in case that the msg3 is a RRCResumeRequest message, a size of the RRCResumeRequest message including the LCID is M bits or N bits.

### Claim 26 (depends on 24)

The UE of claim 24, wherein the at least one processor is further configured to:
receive a UE capability enquiry message from the BS, and
transmit, to the BS, a UE capability information message including RedCap UE capability information.

### Claim 27 (depends on 24)

The UE of claim 24, wherein the at least one processor is further configured to:
in case that a msg4 is received as a response for the msg3, transmit a RRCSetupComplete message to the BS,
wherein the RRCSetupComplete message comprises non access stratum (NAS) container including registration request message to a core network (CN).

### Claim 28

A base station (BS) comprising:
a transceiver; and
at least one processor coupled with the transceiver and configured to:
transmit, to a user equipment (UE), system information including an indicator indicating whether a reduced capability (RedCap) UE is supported on a cell,
in case that the RedCap UE is supported on the cell, receive a msg1 including a random access (RA) preamble from the UE, based on preamble configuration information included in the system information, and
based on a msg2 transmitted as a response for the RA preamble, receive, from the UE, a msg3 including a logical channel identifier (LCD) indicating that the UE is the RedCap UE.

### Claim 29 (depends on 28)

The BS of claim 28,
wherein in case that the msg3 is a RRCSetupRequest message, a size of the RRCSetupRequest message including the LCID is M bits, and
wherein in case that the msg3 is a RRCResumeRequest message, a size of the RRCResumeRequest message including the LCID is M bits or N bits.

### Claim 30 (depends on 28)

The BS of claim 28, wherein the at least one processor is further configured to:
transmit a UE capability enquiry message to the UE, and
receive, from the UE, a UE capability information message including RedCap UE capability information.

### Claim 31 (depends on 28)

The BS of claim 28, wherein the at least one processor is further configured to:
in case that a msg4 is transmitted as a response for the msg3, receive a RRCSetupComplete message from the UE,
wherein the RRCSetupComplete message comprises non access stratum (NAS) container including registration request message to a core network (CN).
