Method and apparatus for RedCap UE identification
RedCap UEs identify themselves based on receive branches and bandwidth during or after random access, allowing networks to apply coverage recovery techniques, enhancing communication reliability and user experience.
Patent Information
- Application Number
- JP2023534253
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-09-30
- Filing Date
- 2021-12-06
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2041-12-06
AI Technical Summary
RedCap UEs face performance degradation due to reduced complexity features, such as fewer receive branches and bandwidth, leading to coverage issues during random access procedures, as the network is unaware of their capabilities before access.
RedCap UEs identify themselves during or after the random access procedure using criteria like receive branches and bandwidth, allowing the network to apply coverage recovery techniques, enabling early identification for improved communication reliability.
Early identification of RedCap UEs enables the network to compensate for coverage losses, improving communication reliability and user experience by optimizing resource allocation and applying appropriate coverage recovery techniques.
Smart Images

Figure 0007592168000017 
Figure 0007592168000018 
Figure 0007592168000019
Abstract
Description
[Technical field]
[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 122,414, filed December 7, 2020, entitled "Multipath Identification of RedCap UEs," and U.S. Provisional Patent Application No. 63 / 250,751, filed September 30, 2021, entitled "Multipath Identification of RedCap UEs," which are incorporated by reference herein as if reproduced in their entirety.
[0002] The present disclosure relates generally to telecommunications and, in particular embodiments, to techniques and mechanisms for identification of reduced capability (RedCap) User Equipment (UE). [Background technology]
[0003] The 3rd Generation Partnership Project (3GPP) is developing and standardizing several key features with the fifth generation (5G) new radio (NR) access technology. In RAN#86 (3GPP RP-201677, July 2020), Rel-17 approved a new Study Item (SI) targeting support for reduced capability (RedCap) NR devices (e.g., User Equipment (UE)). RedCap UEs are NR entities that offer relatively low-end services, but with different requirements than typical cellular UEs, e.g., RedCap UEs may have extremely long battery life. RedCap UEs are envisioned for at least three different scenarios: industrial sensors, video surveillance, and wearables. It is desirable to develop mechanisms to help RedCap UEs communicate. Summary of the Invention
[0004] Technical advantages are generally achieved by embodiments of the present disclosure which describe techniques and mechanisms for identification of reduced capability (RedCap) user equipment (UE).
[0005] According to one aspect of the present disclosure, a method is provided that includes a step of determining, by a user equipment (UE), whether to indicate to a gNB that it is a reduced capability (RedCap) UE during or after a random access (RA) procedure of the UE based on a criterion, where a RedCap UE has a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE or has a bandwidth less than a minimum bandwidth of a non-RedCap UE, and a step of indicating, by the UE to the gNB, that it is a RedCap UE according to the determination result. Optionally, in any of the aforementioned aspects, the non-RedCap UE is a legacy UE. Optionally, in any of the aforementioned aspects, the RedCap UE has one or two receiving branches.
[0006] Optionally, in any of the aforementioned aspects, the minimum number of receive branches for a non-RedCap UE is four for frequency range 1 (FR1) and two for frequency range 2 (FR2).
[0007] Optionally, in any of the aforementioned aspects, the indicating step comprises a step of sending, by the UE, a first message to the gNB when it decides to indicate during the RA procedure, the first message indicating the UE as a RedCap UE during the RA procedure, the first message comprising RA procedure message 1 (Msg1), RA procedure message 3 (Msg3), or RA procedure message A (MsgA).
[0008] Optionally, in any of the aforementioned aspects, the method further includes determining, by the UE, the first message before the RA procedure based on a radio resource control (RRC) configuration broadcast by the gNB and received by the UE before the RA procedure. Optionally, in any of the aforementioned aspects, the RRC configuration comprises criteria information.
[0009] Optionally, in any of the aforementioned aspects, the first message is sent by the UE according to a Physical Random Access Channel (PRACH) configuration broadcast by the gNB before the RA procedure and received by the UE, the PRACH configuration comprising a RACH preamble, a RACH occasion, or a combination thereof, which is related to indicating a RedCap UE.
[0010] Optionally, in any of the aforementioned aspects, the method further includes receiving, by the UE, from the gNB during the RA procedure, a message 2 (Msg2) or a message 4 (Msg4) according to the received coverage restoration technique.
[0011] Optionally, in any of the aforementioned aspects, the first message is Msg1, and the method further comprises repeating transmission, by the UE, of Msg3 to the gNB. Optionally, in any of the aforementioned aspects, the number of repetitions of transmission of Msg3 follows a RACH configuration.
[0012] Optionally, in any of the aforementioned aspects, repeating the transmission of Msg3 is performed when a Reference Signal Received Power (RSRP) measurement of the UE is less than a threshold.
[0013] Optionally, in any of the aforementioned aspects, the indicating step comprises a step of sending, by the UE, to the gNB, when deciding to indicate after the RA procedure, information of a UE capability to indicate the UE as a RedCap UE after the RA procedure is completed.
[0014] Optionally, in any of the aforementioned aspects, the criterion is based on a number of receive branches of the UE, a reference signal received power (RSRP) measured by the UE, a reference signal received quality (RSRQ) measured by the UE, a reference signal strength indicator (RSSI) measured by the UE, or a combination thereof. Optionally, in any of the aforementioned aspects, the criteria is based on a capability of the UE.
[0015] Optionally, in any of the aforementioned aspects, the determining step comprises determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the UE has two receiving branches, or determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has one receiving branch.
[0016] Optionally, in any of the aforementioned aspects, the determining step comprises: determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the UE has two receiving branches and is operable in frequency range 1 (FR1) or FR2; determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has one receiving branch and is operable in FR1 or FR2; or determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has two receiving branches and is operable in FR1.
[0017] Optionally, in any of the aforementioned aspects, the determining step comprises: comparing, by the UE, the RSRP measurement with a threshold configured for RedCap UE; determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the RSRP measurement is greater than the threshold; or determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE's RSRP measurement is less than or equal to the threshold.
[0018] Optionally, in any of the aforementioned aspects, the determining step comprises: comparing, by the UE, the RSRP measurement with a threshold configured for a RedCap UE; determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the UE has two receive branches and the RSRP measurement is greater than the threshold; determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has two receive branches and the RSRP measurement of the UE is less than or equal to the threshold; or determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has one receive branch.
[0019] Optionally, in any of the aforementioned aspects, the determining step comprises: comparing, by the UE, the RSRP measurement with a threshold configured for a RedCap UE; determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the UE has one receiving branch and the RSRP measurement is greater than the threshold; determining, by the UE, to indicate the UE as a RedCap UE during the RA procedure when the UE has one receiving branch and the RSRP measurement is less than or equal to the threshold; or determining, by the UE, to indicate the UE as a RedCap UE after the RA procedure when the UE has two receiving branches.
[0020] According to another aspect of the present disclosure, a method is provided that includes receiving, by a gNB, a first message from a user equipment (UE) during a random access (RA) procedure; determining, by the gNB, whether the first message indicates that the UE is a reduced capability (RedCap) UE, where a RedCap UE has a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE or has a bandwidth less than a minimum bandwidth of a non-RedCap UE; when the first message indicates the UE as a RedCap UE, sending, by the gNB, a second message to the UE during the RA procedure according to a coverage restoration technique; and when the first message does not indicate the UE as a RedCap UE, determining, by the gNB, whether the UE is a RedCap UE after the RA procedure is completed. Optionally, in any of the aforementioned aspects, the non-RedCap UE is a legacy UE. Optionally, in any of the aforementioned aspects, the RedCap UE has one or two receiving branches.
[0021] Optionally, in any of the aforementioned aspects, the minimum number of receiving branches for a non-RedCap UE is four for frequency range 1 (FR1) and two for frequency range 2 (FR2).
[0022] Optionally, in any of the aforementioned aspects, the first message comprises message 1 of an RA procedure (Msg1), message 3 of an RA procedure (Msg3), or message A of an RA procedure (MsgA).
[0023] Optionally, in any of the aforementioned aspects, the first message is based on a physical random access channel (PRACH) configuration broadcast by the gNB, the PRACH configuration comprising a RACH preamble, a RACH occasion, or a combination thereof, which is related to indicating a RedCap UE. Optionally, in any of the aforementioned aspects, the second message is message 2 (Msg2) of the RA procedure or message 4 (Msg4) of the RA procedure.
[0024] Optionally, in any of the aforementioned aspects, the method further comprises receiving, by the gNB, UE capability information from the UE, indicating the UE as a RedCap UE after the RA procedure is completed.
[0025] Optionally, in any of the aforementioned aspects, the method further comprises a step of broadcasting, by the gNB, criteria information to the UE, enabling the UE to decide, based on the criteria, whether to indicate the UE to the gNB as a RedCap UE during or after the RA procedure.
[0026] Optionally, in any of the aforementioned aspects, the criterion is based on a number of receive branches of the UE, a Reference Signal Received Power (RSRP) measurement of the UE, a Reference Signal Received Quality (RSRQ) measurement of the UE, a Reference Signal Strength Indicator (RSSI) of the UE, or a combination thereof. Optionally, in any of the aforementioned aspects, the criteria is based on a capability of the UE.
[0027] Optionally, in any of the aforementioned aspects, the criteria comprises indicating a RedCap UE after an RA procedure when the UE has two receiving branches, or indicating a RedCap UE during an RA procedure when the UE has one receiving branch.
[0028] Optionally, in any of the aforementioned aspects, the criteria comprises indicating a RedCap UE after an RA procedure when the UE has two receiving branches and is capable of operating in Frequency Range 1 (FR1) or FR2, indicating a RedCap UE during an RA procedure when the UE has one receiving branch and is capable of operating in FR1 or FR2, or indicating a RedCap UE during an RA procedure when the UE has two receiving branches and is capable of operating in FR1.
[0029] Optionally, in any of the aforementioned aspects, the criteria comprises indicating a RedCap UE after an RA procedure when the RSRP measured by the UE is greater than a threshold, or indicating a RedCap UE during an RA procedure when the RSRP measured by the UE is less than or equal to the threshold.
[0030] Optionally, in any of the aforementioned aspects, the criteria comprises indicating a RedCap UE after an RA procedure when the UE has two receiving branches and the RSRP measured by the UE is greater than a threshold, indicating a RedCap UE during an RA procedure when the UE has two receiving branches and the RSRP measured by the UE is less than or equal to a threshold, or indicating a RedCap UE during an RA procedure when the UE has one receiving branch.
[0031] Optionally, in any of the aforementioned aspects, the criteria comprises indicating a RedCap UE after an RA procedure when the UE has one receiving branch and the RSRP measured by the UE is greater than a threshold, indicating a RedCap UE during an RA procedure when the UE has one receiving branch and the RSRP measured by the UE is less than or equal to a threshold, or indicating a RedCap UE after an RA procedure when the UE has two receiving branches.
[0032] Optionally, in any of the aforementioned aspects, the method further comprises broadcasting, by the gNB, information indicating that the gNB supports RedCap UEs.
[0033] According to another aspect of the present disclosure, an apparatus is provided that includes non-transitory memory storage comprising instructions and one or more processors in communication with the memory storage, where the instructions, when executed by the one or more processors, cause the apparatus to perform a method in any of the preceding aspects.
[0034] According to another aspect of the present disclosure, a non-transitory computer-readable medium storing computer instructions that, when executed by one or more processors of the device, cause the device to perform the method of any of the aforementioned aspects.
[0035] According to another aspect of the present disclosure, there is provided a system including a user equipment (UE) and a gNB, wherein the UE is configured to determine whether to indicate to the gNB that the UE is a reduced capability (RedCap) UE during or after a random access (RA) procedure of the UE based on a criterion, where a RedCap UE has a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE or has a bandwidth less than a minimum bandwidth of a non-RedCap UE, and indicate to the gNB that the UE is a RedCap UE according to a determination result, wherein the gNB is configured to receive a first message from the UE during the random access (RA) procedure, determine whether the first message indicates that the UE is a RedCap UE, when the first message indicates the UE as a RedCap UE, send a second message to the UE during the RA procedure according to a coverage restoration technique, and when the first message does not indicate the UE as a RedCap UE, determine whether the UE is a RedCap UE after the RA procedure is completed.
[0036] Aspects of the present disclosure allow a RedCap UE to identify that it is RedCap during an RA procedure (early identification) or after the RA procedure (normal identification), allowing for a mix of RedCap UE identification (e.g., some RedCap UEs may perform early identification and some RedCap UEs may perform normal identification). This allows the network to take measures to compensate for link budget loss of RedCap UEs communicating with the network, improving communication reliability and user experience. [Brief description of the drawings]
[0037] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: [Figure 1] FIG. 1 is a diagram of a wireless communication network of one embodiment. [Diagram 2] A diagram showing a four-step random access procedure according to 3GPP TS38.300. [Diagram 3] A diagram showing a two-step random access procedure according to 3GPP TS38.300. [Figure 4] FIG. 1 illustrates a communication network of one embodiment highlighting an example coverage area and number of antennas / branches for a UE. [Diagram 5] FIG. 13 is a diagram of an embodiment operation by a UE for indication of reduced capabilities (RedCap). [Figure 6] FIG. 13 is a diagram of an embodiment operation for route selection based on criterion C1 for indication of RedCap. [Figure 7] FIG. 13 is a diagram of an embodiment of the operation of a gNB for detection of a RedCap UE. [Figure 8] FIG. 13 is a diagram of the operation of an embodiment for route selection based on criterion C4 for indication of RedCap. [Figure 9] 1 is a diagram of a RedCap UE indication method of one embodiment. [Figure 10] FIG. 13 is a diagram of a method for detecting a RedCap UE in another embodiment. [Figure 11] FIG. 1 is a block diagram of a processing system according to an embodiment. [Figure 12] FIG. 2 is a block diagram of a transceiver. [Figure 13] FIG. 1 is a block diagram of an electronic device.
[0038] Corresponding numbers and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The drawings are drawn to clearly show relevant aspects of the embodiments and are not necessarily drawn to scale. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0039] The making and using of the embodiments of the present disclosure will be discussed in detail below. However, it should be understood that the concepts disclosed herein can be embodied in a wide variety of specific contexts, and the specific embodiments discussed herein are merely illustrative and do not serve to limit the scope of the claims. Furthermore, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the present disclosure, as defined by the appended claims.
[0040] A reduced capability (RedCap) user equipment (UE) suffers from performance degradation due to the use of features / techniques that reduce complexity. A RedCap UE may be a UE with a quantity of receiving branches less than the minimum number of receiving branches of a non-RedCap UE, a UE with a bandwidth less than the minimum bandwidth of a non-RedCap UE, and / or other UEs with reduced capability. To compensate for the degradation, coverage restoration techniques such as repetition, lower modulation and coding scheme (MCS) tables, and / or transport block (TB) scaling may be used. Because the gNB is unaware of the presence of a RedCap UE before the UE accesses the gNB, applying these coverage restoration techniques may depend on the UE identifying or indicating that it is a RedCap UE. If the gNB can know early whether the UE is a RedCap UE, the gNB can use one or more of these techniques to improve the performance of that RedCap UE.
[0041] The embodiments of the present disclosure provide a mechanism that allows RedCap UEs to identify themselves during a Random Access (RA) procedure (called early identification) or after the RA procedure (called normal identification). Thus, the embodiments allow a mix of RedCap UE identification, e.g., some RedCap UEs may perform early identification and some RedCap UEs may perform normal identification. This provides flexibility for RedCap UEs to determine when to identify themselves and allows the network to utilize coverage restoration techniques to improve communication performance of RedCap UEs.
[0042] According to one embodiment, the UE may determine whether to indicate to the gNB that it is a RedCap UE during the UE's RA procedure or to indicate to the gNB that it is a RedCap UE after the RA procedure based on a criterion, and then indicate to the gNB that it is a RedCap UE according to the determination result. For example, the UE may indicate that it is a RedCap UE in message 1, message 3, or message A of the RA procedure, or in message 5 after the RA procedure.
[0043] According to another embodiment, the gNB may receive a first message from the UE during an RA procedure and determine whether the first message indicates that the UE is a RedCap UE. When the first message indicates the UE as a RedCap UE, the gNB may send a second message to the UE during the RA procedure according to a coverage restoration technique. When the first message does not indicate the UE as a RedCap UE, the gNB may determine whether the UE is a RedCap UE after the RA procedure is completed.
[0044] 1 illustrates a network 100 for communicating data. The network 100 includes a base station 110 having a coverage area 101, a plurality of mobile devices 120, and a backhaul network 130. As illustrated, the base station 110 establishes an uplink (dashed) and / or downlink (dotted) connection with the mobile devices 120, which serves to carry data and control information from the mobile devices 120 to the base station 110 and vice versa. Data carried on the uplink / downlink connection may include data communicated between the mobile devices 120 and data communicated to / from a remote end (not shown) via the backhaul network 130. As used herein, the term "base station" refers to any entity (or collection of entities) configured to provide wireless access to a network, such as an enhanced base station (eNB), macrocell, femtocell, Wi-Fi access point (AP), or other wireless-enabled device. The base stations may provide wireless access according to one or more wireless communication protocols, e.g., Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. As used herein, the term "mobile device" refers to any entity (or collection of entities) that can establish a wireless connection with a base station, such as user equipment (UE), mobile station (STA), and other wirelessly enabled devices. In some embodiments, network 100 may comprise various other wireless devices, such as relays, low power nodes, etc.
[0045] Figure 2 is a diagram showing a four-step random access procedure according to Figure 9.6.2-1 of 3GPP TS38.300. The entire contention-based random access (CBRA) procedure from Rel-15 is a four-step procedure, as shown in Figure 2, consisting of transmitting a random access preamble (Message 1 (Msg1)) in the PRACH occasion, receiving a random access response (RAR) message (Message 2 (Msg2)) in the physical downlink shared channel (PDSCH) scheduled through the physical downlink control channel (PDCCH), transmitting a message 3 (Msg3) in the physical uplink control channel (PUSCH), and receiving a message 4 (Msg4) in the PDSCH scheduled by DCI in the PDCCH for contention resolution. Before the UE can attempt to access the network, it may need to synchronize (in time and frequency) to the downlink and receive the master information block (MIB) and system information block (SIB) via the physical broadcast channel (PBCH) and PDCCH / PDSCH. After receiving the SIB (mainly SIB1), the UE has knowledge of the physical random access channel (PRACH) configuration and transmission parameters. The random access procedure or process may be referred to as a RACH or RA procedure / process.
[0046] To reduce latency, a two-step procedure for the Random Access (RA) procedure has been standardized in Rel-16 and is shown in Figure 3. The description of the two-step procedure from TS 38.300 is reproduced below.
[0047] "MSGA for two-step RA type includes a preamble on PRACH and a payload on PUSCH. After MSGA transmission, the UE monitors for a response from the network within a configured window. For CFRA, a dedicated preamble and PUSCH resources are configured for MSGA transmission and upon receiving a network response the UE terminates the random access procedure as shown in Figure 9.2.6-1(d). For CBRA, if the contention resolution is successful upon receiving the network response the UE terminates the random access procedure as shown in Figure 9.2.6-1(b), whereas if a fallback indication is received in MSGB the UE performs MSG3 transmission using the UL grant scheduled in the fallback indication and monitors the contention resolution as shown in Figure 9.2.6-2. If the contention resolution is not successful after MSG3 (re)transmission the UE goes back to MSGA transmission."
[0048] That is, in a two-step RA procedure, the UE sends Message A (MsgA) to the gNB, where MsgA includes a preamble on the PRACH and a payload on the PUSCH. The gNB sends Message B (MsgB) in response. In essence, MsgA can be seen as equivalent to sending Msg1 and Msg3 together, and MsgB is equivalent to Msg2 and Msg4.
[0049] A new Study Item (SI) targeting support for reduced capability (RedCap) NR devices (e.g., User Equipment (UE)) was approved in RAN#86 (3GPP RP-201677, July 2020). The SI includes the following objectives: “Identify and study features that reduce potential UE complexity. Reduced number of UE RX / TX antennas UE Bandwidth Reduction Note: Rel-15 SSB bandwidth is reused and L1 changes should be minimized. Half duplex - FDD Relaxed UE Processing Time Relaxed UE processing capabilities.”
[0050] A RedCap UE is an NR entity that provides relatively low-end services, but has different requirements / characteristics than a typical cellular UE (non-RedCap UE). For example, a RedCap UE may have a very long battery life. A RedCap UE may refer to other UEs that have a quantity of receive (Rx or RX) branches that is less than the minimum number of receive branches of a non-RedCap UE, a bandwidth that is less than the minimum bandwidth of a non-RedCap UE, and / or reduced capabilities. A non-RedCap UE may refer to a UE that has the minimum UE requirements specified in Rel. 15 and Rel 16 (3GPP TS38.306, (Release 16), Version 16-2, October 2, 2020). A non-RedCap UE may also be referred to as a legacy UE or a normal UE. As an example, the minimum number of receive branches for a non-RedCap UE is 4 for Frequency Range 1 (FR1) and 2 for Frequency Range 2 (FR2). A RedCap UE may have one or two receive branches. As another example, for FR1 Frequency Division Duplex (FDD) or FR2 bands where a non-RedCap UE is required to be equipped with a minimum of two Rx branches, the minimum number of Rx branches supported by a RedCap UE is one. The work item description (WID) also indicates support of two Rx branches for a RedCap UE. As another example, a RedCap UE may have a maximum bandwidth of 20 MHz for FR1 and 100 MHz for FR2, while a non-RedCap UE may have a minimum bandwidth of 100 MHz and 400 MHz for FR1 and FR2, respectively. As another example, a RedCap UE may have a maximum number of DL multiple-input multiple-output (MIMO) layers (e.g., a RedCap UE with one Rx branch may have a maximum of one MIMO layer, and a RedCap UE with two Rx branches may have a maximum of two MIMO layers). As another example, a RedCap UE may have a reduced maximum modulation order (256QAM in DL is optional). The RedCap UE may support half-duplex (HD)-FDD Type A.
[0051] A receive branch can have one or more receive antennas. A receive branch is associated with a receiver chain. Typically, for FR1, there is one physical antenna per branch. In this case, the number of branches is equal to the number of antennas. For FR2, there is typically a combination of signals of multiple physical antennas (beamforming) in each branch. In this case, it is possible to have multiple, for example 64, antennas per branch.
[0052] Regarding the features of the reduced number of UE antennas / branches in the SI, the following were incorporated in 3GPP TR38.875, Clause 7.2.4, V0.1.0, “Technical Specification Group Radio Access Network; Study on support of reduced capability NR devices” (Release 17) November 25, 2020.
[0053] "In general, RedCap UEs with a reduced number of Rx branches can coexist with legacy UEs. However, the presence of RedCap UEs with a reduced number of Rx branches may impact performance for legacy UEs if some broadcast channels are used for both legacy and RedCap UEs. This means that without early indication of RedCap UEs, both legacy and RedCap UEs will be treated the same by the network, which may result in conservative treatment of all UEs."
[0054] In the scenario studied in SI, it was observed that no compensation on the downlink (DL) was required for Msg2 / Msg4 for RedCap UEs with two RX branches, whereas for RedCap UEs with one RX branch, compensation of up to 6 dB may be required, as described below. Therefore, it is advantageous to have an early identification / indication of RedCap UEs with one 1RX branch, so that Msg2 / Msg4 can be transmitted with appropriate radio parameters due to the performance limitations of the 1RX branch. That is, the RedCap UE may indicate or identify to the network (e.g., gNB) that it is a RedCap UE at an early stage of accessing the network. However, it should be noted that such early identification / indication may not be required (or may be required only rarely) for RedCap UEs with two RX branches. Extended coverage analysis for early access
[0055] The use of techniques and features that reduce complexity may cause coverage degradation, which may be, for example, due to loss of frequency diversity (from having a smaller bandwidth) and / or due to fewer receive branches (loss of diversity and / or spatial multiplexing).
[0056] Several scenarios for coverage recovery evaluation were considered during the random access process of RedCap UE. Both FR1 and FR2 scenarios were considered. Frequency Range 1 (FR1) spans between approximately 600 MHz and 7.25 GHz, and FR2 spans between approximately 24.25 GHz and 47 GHz. Link budgets for several channels and messages were evaluated for example scenarios such as FR1 urban at 4 GHz (scenario 1), FR1 urban at 2.6 GHz (scenario 2), and FR2 indoor (scenario 3).
[0057] As an example, it was assessed that for all FR1 scenarios, a 3 dB loss in link budget due to the small scale form factor may need to be compensated for the PUSCH (including Msg3). For Urban 4 GHz Scenario 1, it was also assessed that when the number of receive branches is 1, 5-6 dB compensation may be required for Msg2 and 2-3 dB compensation may be required for Msg4. A summary of the amount of compensation required for channels and messages for Urban 4 GHz Scenario 1 when the RedCap UE has one receive antenna is shown below in Table 1. Some of the channels and messages may require coverage restoration.
[0058] [Table 1]
[0059] The following is observed: - It was evaluated that a compensation of 3 dB (due to the small form factor) may be required for successful detection of PUSCH / Msg3 at the base station since the UE transmit power may be inaccurate (e.g., minimum power control is used). In the case of a small form factor, the distance between the two receive branches may be closer than a half wavelength. As a result, it is difficult to obtain a 3 dB gain from receive diversity. Another factor is that the estimation of the downlink power may be less accurate in a small form factor, which affects the transmit power for Msg1 and Msg3. For successful detection of PUSCH / Msg3, the UE may have to compensate for the loss using a technique that compensates for coverage, such as repetition. Applying any of the techniques may depend on identifying the UE as a RedCap UE. In other words, the gNB may need to know early in the RACH processing that the UE is a RedCap UE.
[0060] - It has been evaluated that if a RedCap UE has one receiving branch, a coverage loss of 5-6 dB may be required for successful detection of the Msg2 Random Access Response (RAR). Therefore, early identification / indication of UEs as RedCap UEs in Msg1 is needed, which helps the gNB in knowing when to apply coverage restoration techniques to identified RedCap UEs in the downlink. This may also help the gNB in optimizing resources for RedCap UEs and normal (legacy) UEs (UEs that may not require any coverage extension).
[0061] Table 2 below shows the channels and messages that require coverage restoration for urban 4GHz scenario 1 when the RedCap UE has two Rx branches. It is noteworthy that when the number of receive branches is two, coverage restoration is not required for Msg2, Msg4 and PDCCH, as shown in Table 2. That is, for FR1, which includes both FDD and TDD bands, and for the RedCap UE with two Rx branches and reduced antenna efficiency, it is shown that the maximum isotropic loss (MIL) of all downlink channels is better than that of the bottleneck channel for the reference NR UE, and coverage restoration is not required for the downlink channels of the RedCap UE.
[0062] [Table 2]
[0063] Table 3 below shows the UE performance degradation from using 4 Rx branches to 2 Rx branches and from using 4 Rx branches to 1 Rx branch, which is based on a simulation study of an urban scenario in 3GPPTR38.875V0.1.0 (Release 17). CSS represents the common search space and USS represents the UE specific search space.
[0064] [Table 3]
[0065] For successful uplink synchronization and to obtain authorization for initial attachment, messages included in the RACH procedure / processing should not be coverage-limited, which may be the case for RedCap UEs due to complexity reduction features / techniques. To compensate for such losses, coverage recovery techniques may be used. For example, repetition, low modulation and coding scheme (MCS) tables, and / or transport block (TB) scaling may be used to compensate for the loss due to complexity reduction. A discussion of coverage recovery techniques is outside the scope of this disclosure. Since the gNB is unaware of any presence of a RedCap UE before the UE accesses the gNB, applying these coverage recovery techniques may depend on the UE identifying or indicating that it is a RedCap UE. If the gNB can know early in the RACH process whether the UE is a RedCap UE, the gNB can use one or more of these techniques to improve performance for that RedCap UE.
[0066] In addition, while coverage limitations are discussed herein, it should be noted that there are other aspects to consider. As an example, a UE may have coverage but require a large amount of resources to convey the message. In this case, there is a waste of resources that needs to be addressed. As another example, a 5-6 dB penalty (loss) from Msg2 may be handled by always using a repetition factor of 4. However, in this case, the additional overhead (due to the repetition) is quite large and from a resource efficiency perspective, it is much better to compensate only those UEs that actually require compensation. Early Identification Solutions Discussed at RedCap SI In 3GPP TR38.875, v0.1.0, the following options for RedCap UE identification were discussed: "The feasibility, necessity, pros and cons of the following methods for RedCap UE identification are studied. - Option 1: Sending Msg1 - e.g. via a separate initial UL BWP, separate PRACH resources or PRACH preamble splitting - Option 2: Sending Msg3 - Option 3: After Msg4 positive response - for example during Msg5 transmission or part of the UE capability report" A fourth option for a two-step RA procedure (two-step RACH) was also considered early on but was deprioritized during the SI process.
[0067] During the study, it was determined that all three options above are feasible. For example, identification in Msg1 may be possible by providing a PRACH preamble or occasion at a time or frequency associated with the RedCap UE (by configuring configuration information, by standardization in the specification, or via a SIB, etc.). Identification may be in the same initial bandwidth part (BWP) or a separate initial BWP. Similarly, identification in Msg3 may also be possible.
[0068] This early identification allows RedCap UEs and normal UEs to be treated differently, as opposed to having to treat all UEs (both RedCap and normal) conservatively due to the possible presence of RedCap UEs, if the RedCap UEs have worse performance than normal (legacy, non-RedCap) UEs. The worse performance may be due to reduced complexity features such as a smaller number of receive branches, or due to antenna performance loss due to the smaller form factor. Early Access for LTE-M Devices
[0069] In Rel-13, the network indicates support for Long Term Evolution Machine Type Communication (LTE-M) devices by sending an indication of PDSCH for SIB1 in the MIB. Initial access for Machine Type Communication (MTC) devices is defined in 3GPP TS 36.213 and 36.331. RACH processing for LTE-M devices has much commonality with regular LTE RACH processing and the protocols / messages exchanged are identical.
[0070] An MTC UE does not formally identify itself as an MTC device until it sends its UE category. However, some MTC UEs suffer from coverage limitations. Therefore, the RACH preamble (Msg1) and MPDCCH / PDSCH (Msg2 and Msg4) may be repeated many times. Different coverage levels (also called coverage extension (CE) levels) are defined based on the Reference Signal Received Power (RSRP) and are defined in the information element (IE) of the RSRP-ThresholdsPrachInfoList specified in TS36.331, v16.2.1, as shown in Table 4 below.
[0071] [Table 4]
[0072] The existing PRACH-Config in Rel-12 has been enhanced to include RSRP-ThresholdsPrachInfoList as per TS 36.331, v16.2.1, as shown in Table 5 below.
[0073] [Table 5]
[0074] In addition, RACH-ConfigCommon includes a new IE, rach-CE-LevelInfoList, which is a list of rach-CE-LevelInfo according to TS36.331, v16.2.1, as shown in Table 6 below (rach-CE-LevelInfoList-r13).
[0075] [Table 6]
[0076] The rach-CE-LevelInfo contains the per UE physical parameters at a given CE level expected for the RACH as shown in Table 7 below.
[0077] [Table 7]
[0078] All these IEs are nested in a SIB as specified in TS 36.331.
[0079] In this regard, it is possible to have normal UEs (legacy) share the PRACH region with the best aligned (in terms of channel gain conditions, RSRP) LTE-M UEs.
[0080] Identification of a UE at a given CE level as an LTE-M UE is performed upon reception of Msg1 at the base station. The UE selects the appropriate preamble according to RSRP. The base station does not know the amount of coverage extension required until it receives Msg1. The network is unaware of the presence of an LTE-M device in the configured uplink resources until it receives Msg1. However, the following aspects should be noted. Early identification is performed based on the selected RACH resource, which the UE determines based on the RSRP.
[0081] · Although UEs of various CE levels are identified in Msg1, there is no case where MTC UEs are identified in Msg1 while others are identified in Msg5, and such a process is practically impossible to achieve in the current LTE framework since the base station has to monitor MTC UEs occupying a limited number of PRBs (6). Therefore, it is mandatory that MTC UEs are identified in Msg1 so that Msg2 can be properly received.
[0082] The embodiments of the present disclosure provide a mechanism that allows a UE to identify itself as a RedCap UE by Msg5 (or later UE capability exchange) or by early identification in Msg1, etc. That is, at the same time, the gNB may provide a configuration that allows some RedCap UEs to be identified early while others are identified at a later stage (as opposed to all RedCap UEs being identified at the same time - early or not). Some RedCap UEs may have a similar identification as normal UEs (using the current initial access process) until the exchange of capability to be identified as RedCap UEs, while other RedCap UEs may be identified at the Msg1 or Msg3 stage. In the latter case, the exchange of additional capabilities may occur after (or in) Msg5 after the RA procedure.
[0083] Compared to the dedicated initial access procedure for LTE-M devices, the proposed solution for RedCap UE identification allows a mix of identifications (some in early stages - Msg1 or Msg3, others in Msg5). Note that using dedicated resources is not excluded from this solution.
[0084] In some embodiments, RedCap UE types may be defined (types may differ based on, for example, the number of receive antennas, the bandwidth supported, or a combination thereof), in which case different types of RedCap UEs may be handled in terms of when the identification is done along separate paths, i.e., at different stages of the RACH procedure. In this case, the gNB may be able to avoid having to identify all UEs in Msg5, and may also be able to avoid having to identify all UEs in Msg1 or Msg3. With such a solution, optimization based on RedCap UE types is possible. In one embodiment, RedCap UE types are defined based on the number of receive antennas / branches that the RedCap UE has, or the bandwidth supported, or both.
[0085] As used herein, identifying or indicating that a UE is a RedCap UE may be referred to as RedCap UE identification or indication, or UE identification or indication, for convenience of description. Identification or indication of a RedCap UE before (or during) the random access procedure is completed, e.g., at Msg1, Msg3, or MsgA stage, may be referred to as early identification or indication, or early stage identification or indication. Identification or indication of a RedCap UE during the exchange of capabilities after the random access procedure is completed, as has been conventionally performed, may be referred to as later (or regular or standard) identification or indication, or later stage identification or indication, for convenience of description. In the following description, the term "path" is used to indicate a method or manner of indicating / identifying a UE as a RedCap UE, e.g., by early identification / indication or later identification / indication, unless otherwise specified. The terms "identifying a UE (or identifying a UE, UE identification)" and "indicating a UE (or indicating a UE, UE indication)" are used interchangeably. Hereinafter, for convenience of explanation, a "RedCap UE with n Rx branches" may be simply referred to as an "nRX RedCap UE", an "nRX UE", or a "UE with nRX", where n is an integer greater than 0. In some embodiments, two routes, route A and route B, are defined to indicate that a UE is a RedCap UE.
[0086] Path A: The UE is identified as a RedCap UE during Msg5 (exchange of capabilities). One or more of the UE capabilities / features / feature sets of the UE can be used to identify the UE as a RedCap UE. This can be by use of one individual UE capability (e.g., a feature such as RedCap UE is defined) or by a set of existing and / or new UE capabilities (e.g., UE bandwidth, number of antennas, etc.). In such a case, when some of the UE features are selected from a given set of combinations (e.g., BW 20 MHz, 1 RX antenna), the gNB knows that the UE is a RedCap UE.
[0087] Path B: The UE is identified as RedCap prior to Msg5. This could be, for example, during the transmission of Msg1, MsgA, or Msg3. The UE may inform the network that it is a RedCap UE either implicitly (e.g., by using the preamble / resource selection for transmitting Msg1) or explicitly (e.g., by setting a bit in Msg3).
[0088] Path A corresponds to later identification or indication, and path B corresponds to early identification or indication. Path B may also be referred to as the early path. Path A may also be referred to as the canonical path, later path, or normal path. Note above that path A is associated with Msg5, and path B is associated with Msg1, Msg3, or MsgA.
[0089] 4 is a diagram illustrating an embodiment communication network 400 highlighting example coverage areas and number of antennas / branches for UEs. As shown, network 400 includes a gNB 410, which has a coverage area 412 for a UE with one Rx branch and a coverage area 414 for a UE with two Rx branches. RedCap UEs 422 and 424 each have one Rx branch. RedCap UEs 426 and 428 each have two Rx branches. UEs 422 and 426 in coverage area 412 and UE 428 in coverage area 414 may use path A to indicate that they are RedCap UEs. UE 424 in coverage area 414 may use path B to indicate that it is a RedCap UE.
[0090] In some embodiments, criteria may be defined for a UE to select / determine whether path A or path B is used for RedCap UE identification. The following provides example criteria (C) C1 and C2. C1: Selection of Path A or Path B is based on the number of receive antennas in the RedCap UE: o UE with 2RX (2 Rx antennas / branches) uses Path A o UE with 1RX (1 Rx antenna / branch) uses path B C2: Selection of Path A or Path B is based on the number of receive antennas and duplex mode of RedCap UE: o UE with 2RX uses FR1 FDD and route A in FR2 o UE with 1RX uses FR1 FDD and path B in FR2 o UE with 2RX uses path B in FR1 TDD
[0091] According to criterion C1, when the UE has two receiving branches, the UE may indicate it as a RedCap UE after the RA procedure, and when the UE has one receiving branch, it may indicate it as a RedCap UE during the RA procedure.
[0092] According to criterion C2, when a UE has two receive branches and can operate in FR1 FDD band and FR2 band, it may indicate that it is a RedCap UE after RA procedure. When a UE has one receive branch and can operate in FR1 FDD band and FR2 band, it may indicate that it is a RedCap UE during RA procedure. When a UE has two receive branches and can operate in FR1 TDD band, it may indicate that it is a RedCap UE during RA procedure. It should be noted that currently, FR2 is defined as TDD. The above criteria C1 and C2 are defined based on the number of Rx antennas. A RedCap UE may support operation on one or multiple frequency bands. However, it should be noted that according to the goal of WID, a RedCap UE is not allowed to operate on more than two frequencies simultaneously. In this case, criterion C2 may also be applied with some modifications. For example, C2 may be modified to specify that a UE with 2RX uses path A when the UE is capable of operating in FR1 FDD or FR2, and a UE with 1RX uses path B when the UE is capable of operating in FR1 FDD or FR2. Thus, implementation of the embodiment criteria for path selection may vary depending on whether a RedCap UE is permitted to operate in one or more frequency bands. Those skilled in the art will recognize that various modifications, alternatives, and embodiments of the criteria may be applicable to a UE selecting a path to identify that it is a RedCap UE without departing from the spirit and principles of the present disclosure.
[0093] In some embodiments, the criteria may be based on bandwidth or band. As an example, for a first band (or multiple first bands) with a bandwidth larger than 20 MHz, the RedCap UE may use early indication, and for a second band (or multiple second bands) with a bandwidth equal to or smaller than 20 MHz, the RedCap UE may indicate itself as a RedCap UE during capability exchange (Msg5).
[0094] In some embodiments, the criterion may also be determined based on one or more other parameters, such as parameters indicative of wireless channel conditions, including RSRP (before or after antenna combining), Reference Signal Received Quality (RSRQ), Reference Signal Strength Indicator (RSSI), etc. As an example, a possible criterion C3 may be as follows: C3: Route A or Route B selection is based on RSRP after antenna combination o UEs with RSRP > threshold use Route A. o UEs with RSRP ≤ threshold use route B
[0095] In general, the estimated signal quality may be performed for each branch individually and the best signal quality may be used. The signal quality evaluation may be based on two or more branches where the signals from the antennas / branches are combined. For example, the received power evaluation may be based on the sum (in the linear domain) of the evaluations for each branch. In a particular example, the evaluation of one RSRP is -80 dBm, the evaluation of the second RSRP is -83 dBm, and the combined evaluation is -78.2 dBm.
[0096] According to criterion C3, the UE may compare the RSRP measurement with a threshold configured for RedCap UE for identification. When the RSRP measurement is greater than the threshold, the UE indicates it as a RedCap UE after the RA procedure. When the RSRP measurement of the UE is less than or equal to the threshold, the UE indicates it as a RedCap UE during the RA procedure.
[0097] C3 has a single threshold for the UE. In some embodiments, the UE may select or modify the single threshold provided based on its type (RedCap type as described above) or function, assuming that the difference between different thresholds does not naturally appear on the RSRP metric used by the UE to determine which path to use. For example, if the RSRP measurement is 3 dB and there are twice as many RX antennas, there may be no need for multiple thresholds. However, a factor may be added to the threshold using other means (e.g., RSRP measured with only one antenna). Or, optionally, a small form factor dB based correction may be performed on the threshold.
[0098] The threshold value may be associated with a coverage area. For example, the "Coverage area 412 for UEs with one RX antenna" in FIG. 4 may be associated with a first threshold value, and the "Coverage area 414 for UEs with two RX antennas" in FIG. 4 may be associated with a second threshold value. UEs in the coverage areas 412 and 414 may use the corresponding threshold value to determine a path for RedCap UE indication. For C3, the RSRP measure may be determined based on measurements performed on, for example, SSB blocks or demodulation reference signals (DMRS) for PDCCH. Those skilled in the art will recognize that various measurements of RSRP may be applied to the embodiments of the present disclosure.
[0099] FIG. 5 is a flow diagram 500 illustrating operation of an embodiment by a UE. The UE may obtain a path selection criterion (block 502). The UE needs to know the path selection criterion, e.g., C1, C2, or C3. There may be several possibilities for the UE to obtain the path selection criterion. In one embodiment, the standard specification may specify which path to use by the UE. For example, for C1, the UE behavior may be hard-coded in the standard specification with a sentence, e.g., "A RedCap UE with one receive antenna identifies itself in Msg1 or in Msg3". This may indicate that C1 or C2 should be used by the UE. In one embodiment, which path to use by the UE for RedCap UE indication may be pre-configured for the UE. As an example, which path to use may be indicated in a SIB or other signaling message. For example, for C3, the network / base station may indicate the RSRP threshold in the SIB. This may indicate that C3 should be used by the UE. The network may implicitly or explicitly signal which of the criteria should be used to identify a RedCap UE.
[0100] The UE may obtain a path configuration (block 504). The UE needs to know a) whether multiple paths exist and b) what configuration there is for path B. For a), there may be a case where one path (e.g., path A) is configured. For example, in a dense deployment scenario where gNBs are close to each other, it is expected that even a RedCap UE with only one RX antenna is enough to communicate with the gNB without CE means. Therefore, a parameter in the SIB may indicate that only one path is configured. This signaling may be explicit based on the configuration for b). For b), the UE needs to obtain a resource configuration for early identification in this example. For example, if the identification is performed in Msg1 / MsgA or Msg3, the RedCap UE needs to know which parameters (time resource / PRB / preamble) should be used for early indication. Signaling similar to that used for LTE-M devices with various CE levels may be used. In general, the path configuration may include information about available paths to use, RACH configuration for early indication (time frequency resources and / or preamble), and / or information indicating whether path B is implemented during Msg1 or Msg3, or MsgA.
[0101] The UE may determine / select a path to use (block 506). When the RedCap UE gets all the relevant RACH configuration parameters, it needs to determine which path to use. In some cases, this operation is trivial and nothing needs to be done (e.g., for C1, the RedCap UE knows the number of antennas it has and it can directly select the corresponding path). However, in some cases, this decision requires additional operations. For example, for C3, the RedCap UE needs to perform RSRP measurements to select a path.
[0102] The UE may identify itself as RedCap according to the selected path (block 508). Once the path is selected, the RedCap UE proceeds according to the selected path. For example, if path A is selected, the UE may not need to do anything special and may simply send its capabilities (indicating that it is a RedCap UE) during capability exchange after RACH processing. If path B is selected, which may indicate identification in Msg1 for example, the RedCap UE needs to select a set of resources (time resources / PRB / preamble index) as indicated / configured by the gNB for early identification (path B).
[0103] FIG. 6 is a diagram 600 illustrating the operation of an embodiment for path selection based on criterion C1. A UE (RedCap UE) may obtain a path configuration from a SIB (block 602). The path configuration may be similar to that described in block 504 of FIG. 5. The UE may then check whether it has one Rx antenna (block 604). When the UE has two or more Rx antennas, the UE may perform regular identification, i.e., path A (block 606). That is, the UE may identify that it is a RedCap UE after the RACH procedure, e.g., during a capability exchange between the UE and the network. When the UE has one Rx antenna, the UE may perform early identification, i.e., path B (block 608). That is, the UE may identify that it is a RedCap UE during the RACH procedure, e.g., during the transmission of Msg1, Msg3, or MsgA.
[0104] FIG. 7 is a diagram 700 illustrating the operation of an embodiment of a gNB. The gNB may check whether it supports RedCap UEs (block 702). If the gNB does not support RedCap UEs, the gNB may exclude the RedCap UEs (block 704). In this case, the gNB may not serve the RedCap UEs. If the gNB supports RedCap UEs, it may check whether it supports coverage restoration (block 706). If the gNB does not support coverage restoration, the gNB may detect the RedCap UE according to path A (block 708). That is, the gNB may know that the UE is a RedCap UE based on the indication / identification performed according to path A. If the gNB supports coverage restoration, the gNB may provide the UE with parameters for coverage restoration (block 710). The gNB may perform early detection (block 712). That is, the gNB may detect whether the UE indicates / identifies that it is a RedCap UE, for example, in Msg1, Msg3, or MsgA (according to path B) during the UE's RACH procedure. If the gNB does not detect an indication / identification from the UE during early detection (according to path B), the gNB may detect the UE according to path A (block 714), i.e., the gNB detects a RedCap UE after the RACH procedure. If the gNB detects an indication / identification from the UE during early detection, the gNB may apply coverage restoration measures to communicate with the UE (block 716). As an example, if the UE indicates in Msg1, the gNB may apply coverage restoration measures for all DL transmissions to the UE after receiving Msg1 during the RACH procedure. If the UE indicates in Msg3, the gNB may apply coverage restoration measures for all DL transmissions to the UE after receiving Msg3 during the RACH procedure. If the UE indicates in MsgA, coverage restoration measures may be applied to transmit MsgB to the UE. The UE may apply the received coverage restoration techniques to receive these DL transmissions. In the uplink, the UE may repeat the transmission of messages during the RA procedure.If both the UE and the network support Msg3 repetition, the UE may repeat transmission of Msg3 according to the configuration for repetition. Msg3 may also be retransmitted based on the HARQ procedure, which may incur a larger delay.
[0105] For the FR1 TDD band, where normal UEs use four RX branches, 2RX RedCap UEs and 1RX RedCap UEs have different behavior than normal UEs (e.g., due to fewer branches), and therefore, forcing 2RX UEs to use the normal path may require some conservative handling for both RedCap UEs and non-RedCap UEs. Based on the frequency band, there may be a distinction between RedCap UEs and non-RedCap UEs. In this case, the identification of RedCap UEs can be done in the framework described above, with a criterion taking the number of RX antennas (1, 2, or 4) as well as the band as input parameters. Based on the indication, the network may take measures to compensate for communication with RedCap UEs. If criterion C1 is used for FR1 TDD, 2Rx UEs may use the normal path if conservative handling is used. This may not be the case for other bands.
[0106] In some embodiments, whether a RedCap UE capable of operating in FR1 TDD band identifies itself according to a normal or early path may be configured / indicated by a SIB configuration. As an example, a SIB configuration may be broadcast to include the path selection criteria and parameters to use for different paths. As another example, the gNB may simply add a field to the SIB to indicate which path to use (e.g., always use path B). Similarly, for RedCap UEs capable of operating in FDD bands where 4RX is mandatory for legacy UEs, a SIB may be broadcast to indicate the path configuration and path selection criteria for the UE to determine the path.
[0107] In some embodiments, as described in C3, the instantaneous channel conditions, e.g., channel conditions as represented by RSRP after antenna combining, may be considered by the UE to determine which path to use. In one embodiment, a RedCap UE may identify itself as a RedCap UE using the normal path if the channel conditions are within a threshold configured for the normal path. In this way, if a RedCap UE with 2RX is in a particularly bad state, it can be accessed as if it were a 1RX UE, and a 1RX UE in a particularly good state can be accessed as if it were a 2RX UE.
[0108] In some embodiments, a criterion for a RedCap UE to select a path may be defined such that one of a 1RX RedCap UE or a 2RX RedCap UE may select a path. The following provides such an exemplary criterion C4: C4: Selection of Path A or Path B is based on RSRP after antenna combining for UE with two RX antennas: o UE with 2 RX antennas and RSRP > threshold will use Path A o UEs with 2 RX antennas and RSRP ≤ threshold use path B o UE with one RX antenna uses path B Or: C5: Selection of Path A or Path B is based on RSRP after antenna combining for UE with one RX antenna o UE with 1 RX antenna and RSRP > threshold will use Path A o UEs with 1 RX antenna and RSRP ≤ threshold use path B o UE with two RX antennas uses path A
[0109] In the above criteria (C4 and C5), the use of threshold to select a path is based on the characteristics of RedCap UE. One RedCap UE is a UE with two RX antennas, and the other is a UE with one RX antenna. For example, in C4, only 2Rx RedCap UEs are allowed to use RSRP threshold to select a path, while UEs with 1Rx are not allowed to use RSRP. 1Rx UEs always use path B, i.e. early identification.
[0110] The rationale for C4 is that it may be desirable to not allow 1RX UEs to use the normal path even if they have good channel conditions, to prevent too many UEs from using the normal path and initial access resources such as PRACH preambles. The rationale for C5 is similar. In one example, a semi-static partitioning of RACH resources between path A and path B may be possible, without having to consider the individual radio conditions of each RedCap UE.
[0111] In C5, only RedCap UEs with 1Rx are allowed to use RSRP threshold to select a route, where the UE can be identified earlier or at a later stage. 2Rx UEs always use route A.
[0112] In all these example criteria above, the gNB may have RedCap UEs that meet different criteria and may be identified at different stages. For example, some RedCap UEs may be identified at an early stage (early identification), while some other RedCap UEs are identified at a later stage. After identification of RedCap UEs by either Path A or Path B, full capability exchange may occur at a later stage, such as Msg5.
[0113] FIG. 8 is a diagram 800 illustrating the operation of an embodiment for route selection based on criterion C4. A UE (RedCap UE) may obtain route configuration from a SIB (block 802). The route configuration may be similar to that described in block 504 of FIG. 5. The UE may then check whether it has two Rx antennas and whether the RSRP measurement is greater than a threshold (block 804). When the UE has two Rx antennas and the RSRP measurement is greater than a threshold, the UE may perform regular identification, i.e., route A (block 806). When the UE does not have two Rx antennas or the RSRP measurement is not greater than a threshold, the UE may perform early identification, i.e., route B (block 808). This example may be combined with the example shown with respect to FIG. 6, where a 1Rx RedCap UE always uses early identification.
[0114] In the above embodiment, two routes are described. However, it should be noted that more than two routes may be defined. For example, three routes may be defined, corresponding to identification by Msg1, Msg3, and Msg5, respectively. The UE may determine, for example, based on a network configuration or criteria, which of the routes it should use to identify itself as a RedCap UE. In this case, when multiple (more than two) routes are available, the selection of the route may be based on several different embodiments, considerations, and / or factors. For example, the selection may be as follows: Threshold-based (e.g. RSRP) UE implementation based (e.g. the UE has knowledge of its own antenna imperfections) Traffic based (e.g. the UE has knowledge of its subscriptions or other information that is normally communicated after RRC connection).
[0115] If there are “high-end” and “low-end” wearables, the criteria for selecting a path may be based on the type of wearable. For example, a high-end wearable may use path A, and a low-end wearable may use path B.
[0116] Although the embodiments of the present disclosure are described for a RedCap UE, they are applicable to other scenarios such as low-end smartphones, "regular" UEs requiring extended coverage, industrial sensors, etc.
[0117] The following describes an embodiment of Msg5 identification (ie, RedCap UE identifies it as RedCap-path A in Msg5 (during capability exchange).) Msg5 identification may also be referred to as Msg5 path identification in the following description.
[0118] There are different possible paths for RedCap identification, one of which is a typical Msg5 after RACH processing or after UE function exchange, where the UE informs the gNB of its characteristics, which may include an indication or identification that it is a RedCap UE. In addition to the RedCap feature, this solution does not actually require any standard changes. In one embodiment, a RedCap UE with two Rx antennas can be identified using Msg5 path identification. In another embodiment, a RedCap UE with one Rx antenna but with very strong channel gain conditions (e.g., RSRP greater than the RSRP threshold) can also use Msg5 path identification. This identification path may be combined with other identification paths through Msg1 or Msg3, as described later in this disclosure.
[0119] The following describes an embodiment of Msg1 identification (i.e., RedCap UE identifies it as RedCap-path B in Msg1 (during RACH processing)). As mentioned above, one possible way to identify a RedCap UE is by early path identification, such as during Msg1 transmission by the RedCap UE. The configuration for this path may be provided in the SIB. For example, identification in Msg1 may be possible by providing (by configuration information, by specifying a standard specification, or in the SIB, etc.) a PRACH preamble or occasion at a time or frequency associated with the RedCap UE. These may be in the same initial BWP or in a separate initial BWP. The early path identification may be performed in the same or separate initial UL BWP as the initial UL BWP normally used for identification. Information about the initial BWP may be broadcast in the SIB. There may be different RACH configurations associated with different initial UL BWPs.
[0120] In one example, the PRACH configuration may be broadcast in a SIB, where the PRACH configuration includes information used to identify RedCap UEs using path B. As an example, the PRACH configuration may include information of a PRACH preamble, a RACH occasion, or a combination thereof, which is related to indicating / identifying RedCap UEs. As mentioned above, other messages in the RACH process, such as Msg3 or MsgA, may also be used for early identification of RedCap UEs. Which of Msg1, Msg3, or MsgA should be used for early identification may be configured by a Radio Resource Control (RRC) configuration. The RRC configuration may be broadcast by the gNB. Upon receiving the SIB, the UE will have knowledge of the PRACH configuration and transmission parameters, such as one or more of the following: PRACH preamble format Time-frequency resources Parameters for determining the route sequence A cyclic shift in the sequence set of the PRACH preamble, or Index into the logical root sequence table, unregulated association set type, regulated Type A or Type B
[0121] For a normal NR UE, in accordance with TS38.331, v16.2.0, the time domain location for the PRACH preamble is determined by the RRC parameter prach-ConfigurationIndex, and the frequency domain resource for the PRACH preamble is determined by the RRC parameters msg1-FDM and msg1-FrequencyStart.
[0122] In one embodiment, RedCap UEs using early path identification (e.g., RedCap UEs with 1Rx, or RedCap UEs with 2Rx but RSRP<threshold) may have a separate PRACH configuration (also called RACH configuration) information element from normal UEs, e.g., RACH-ConfigGeneric-RedCap information element, where the RACH configuration information element specifies RedCap random access parameters as indicated by the suffix. In this information element, frequency and time resources may be indicated by parameters prach-ConfigurationIndex-redcap, msg1-FDM-redcap, and msg1-FrequencyStart-redcap. Other configuration naming may include v17 and / or abbreviation rc(RedCap), and is not limited to the above examples. RedCap UE PRACH (or RACH) configuration is not limited to time, frequency location, and may also include resource periodicity, subcarrier offset, number of subcarriers, maximum number of preamble transmissions and power ramping steps, start slot number, number of slots, etc. Thus, a RedCap UE may receive a separate configuration from a normal UE for early identification, or a RedCap UE may use a later step for identification as a normal UE does.
[0123] In another embodiment, the same RACH-ConfigGeneric information element may include PRACH configurations for both RedCap UEs that are identified at a later stage (through Msg5) and RedCap UEs that are identified at an earlier stage (e.g., through Msg1). In another embodiment, the PRACH resources may not overlap for different types of RedCap UEs that are to be identified at different stages, in which case there may be information elements for different types of UEs defined to configure indications for RedCap UEs.
[0124] In another embodiment, the gNB may indicate that RedCap UEs with 2Rx (which may not require coverage compensation) may use a legacy PRACH configuration, while RedCap UEs with 1Rx may use a different PRACH configuration. In yet another embodiment, resources for RedCap UEs that should be identified at an early stage may be specified in terms of an offset from resources configured for normal UEs. The offset may be in terms of a time-frequency resource offset. It should be noted that distinct configurations are not limited to time-frequency resource location configurations, but may include all other configurations associated with the RACH procedure, such as different preambles.
[0125] An example embodiment of the configuration IE is provided below in Table 8. In this example, a separate general PRACH resource is configured (in italics) for RedCap UEs that perform early identification. RedCap UEs do not use the PRACH configuration for normal UEs, but use a separate PRACH configuration.
[0126] [Table 8]
[0127] In another embodiment, the threshold is defined when RedCap UE uses early identification path using threshold based on criteria (C3, C4, C5, etc.). In one embodiment, the threshold may be defined using rsrp-ThresholdsPrachInfoList-r17 IE. Different coverage levels may be defined based on RSRP and may be defined in the information element. RACH-ConfigGeneric IE may be enhanced to include rsrp-ThresholdsPrachInfoList-r17 IE. In another embodiment, RACH-ConfigCommon IE may be enhanced to include rsrp-ThresholdsPrachInfoList-r17 IE.
[0128] In another embodiment, the network may also configure a set of preambles that are to be specifically used by RedCap UEs that are to be identified in Msg1. These preambles may have different characteristics than the preambles configured for normal UEs. The characteristics that may be different may include one or more of the following: type of sequence, cyclic shift, etc.
[0129] Different groups of preambles may be defined: in one embodiment, two groups of preambles are defined, one group configured for UEs that are identified early, with or without a threshold, and the other group configured for UEs that are identified later.
[0130] Upon identifying the RedCap UE PRACH resource via the PRACH configuration, the UE may transmit a PRACH preamble (random access preamble) to the gNB (at the PRACH occasion) accordingly. The gNB may calculate the RA-RNTI associated with the RACH occasion (RO) on which the random access preamble is transmitted, and the parameters used to calculate the RA-RNTI may include the time and frequency resource on which the preamble is transmitted, as indicated by prach-ConfigurationIndex-redcap, msg1-FDM-redcap, and msg1-FrequencyStart-redcap. Because a RedCap UE may require the preamble to be transmitted multiple times (e.g., for uplink coverage extension), a configuration including the maximum number of allowed repetitions may be configured for the RedCap UE, e.g., in the SIB. The number may be associated with the coverage extension level.
[0131] In the second step of the RACH process (with reference to FIG. 2), following the transmission of the PRACH preamble, the UE waits for a random access response from the gNB. The random access response (RAR) may be sent through a DCI scrambled with the RA-RNTI value. The UE may attempt to detect a PDCCH (i.e., DCI) with a corresponding RA-RNTI within the ra-ResponseWindow period. In another embodiment, a RedCap UE with 1Rx (or a RedCap UE with 2Rx and poor channel gain conditions (e.g., RSRP less than a threshold)) may be configured with a separate period ra-ResponseWindow-redcap from normal UEs to monitor DCI.
[0132] The criteria for path selection may be configured using the configuration received in the SIB as described above, but the criteria may also be incorporated in the technical specification. For example, the specification may state that a 2 Rx branch RedCap UE operating in a band supporting a minimum of 2 Rx branches for non-RedCap UEs may identify itself using path A, and a 1Rx RedCap UE may identify itself using path B. Also, the use of path A by a 2Rx RedCap UE may be further determined based on whether some RAN4 performance requirements are met. As an example, a 2RX UE with a very small form factor and poor receiving performance due to antenna correlation may use path B.
[0133] If the UE performs early identification using Msg1, in some embodiments, the following may be considered for other steps in a four-step random access procedure, by way of example:
[0134] In some examples, to receive Msg 2 (or Msg2), the UE may receive the associated PDCCH (associated with Msg2) using a downlink coverage extension technique (or a technique that compensates for downlink performance) for the associated PDCCH. The following may be considered. When there is a dedicated PDCCH for early identification
[0135] o The UE may receive a PDSCH carrying Msg2 via one or more coverage extension techniques, which may be signaled via DCI in the PDCCH. Downlink coverage extension techniques may include, for example, TB scaling, repetition, and / or lower MCS levels - Note that when coverage extension is applied, the timing for the RACH (e.g., Msg3 transmission) may change. When there is no dedicated PDCCH for early identification o The UE can receive the PDSCH using one or more downlink coverage extension techniques provided by the SIB configuration. - Note that when downlink coverage extension is applied, the timing for RACH may change.
[0136] In some examples, to send Msg 3 (or Msg3) when early identification is performed in Msg1, some options may include: No changes to the RAR UL permission, i.e. use the UL permission received in the RAR for sending Msg3 Modify the RAR UL permissions (e.g. by using TB scaling, different MCS levels, and / or repetitions) · Enhance RAR UL authorization using SIB configuration (e.g., perform uplink coverage enhancement such as Msg3 repetition based on SIB configuration).
[0137] In some examples, to receive Msg 4 (or Msg4) when early identification is performed in Msg1, the base station (e.g., gNB) may reuse the technique for sending Msg2 PDCCH to schedule Msg4. Since the base station has a better understanding of the UE (the UE identifies it as a RedCap UE in Msg1), it may use the configured parameters for the transmission of the PDCCH for Msg4. Note that at this point, the base station may use that UE's individual temporary RNTI rather than the RA-RNTI. Now, the signaling is "mostly" individual since the temporary RNTI is individual to that particular UE, and the PDSCH scheduling may be tailored for that UE.
[0138] The following describes an embodiment of Msg3 identification (i.e., RedCap UE identifies it as RedCap-path B in Msg3 (during RACH processing)). As mentioned above, Msg3 may be used for early identification of RedCap UEs. This early identification allows RedCap UEs and normal UEs to be treated differently, as opposed to having to treat all of the UEs (both RedCap and normal) conservatively due to the possibility of a RedCap UE being present, if the RedCap UE has worse performance than a normal UE.
[0139] In one embodiment, one or more bits in Msg3 may be used to identify RedCap UEs that have gone through the early identification path. In NR RACH processing, RACH-ConfigCommon is used to configure parameters related to Msg3, such as the transform precoder in RACH-ConfigCommon. In one embodiment, one bit in Msg3 may be used to explicitly identify the UE as a RedCap UE. In another embodiment, if the Msg3 size exceeds a certain threshold, a bit in another field of Msg3, such as the transform precoder field, may be used to identify the UE as a RedCap UE. Table 9 below shows an example RACH-ConfigCommon IE that includes msg3-transformPrecoder (msg3-transformPrecoder, in italics).
[0140] [Table 9-1]
[0141] [Table 9-2]
[0142] In one embodiment, a separate information element, whose functionality is similar to the RACH-ConfigCommon functionality, but with different values configured for RedCap UEs, may be used for the purpose of configuring RedCap and provides configuration information for RedCap UEs to be identified at an early stage.
[0143] The gNB receives Msg3 and can therefore identify the RedCap UE based on Msg3 and the configuration used. Msg3 can be sent by the UE using a coverage restoration technique. When the gNB knows that Msg3 is transmitted using a coverage restoration technique, it can accurately detect Msg3 and can further transmit Msg4 for the RedCap UE using a downlink coverage restoration technique, such as repeating Msg4 several times and / or using a lower MCS value or TB scaling. The following describes Coverage Extension (CE).
[0144] Msg3 repetition is an optional feature for non-RedCap UEs. Conventionally, Msg3 repetition may be used to provide uplink coverage extension for transmitting Msg3 by non-RedCap UEs. Msg3 may be transmitted repeatedly (multiple times) by the UE during RACH processing. Msg3 repetition may be referred to as a "CE feature" hereinafter. The gNB may configure a RACH occasion (RO) and / or preamble that a non-RedCap UE may use to perform Msg3 repetition. In one example, a non-RedCap may perform Msg3 repetition for coverage extension if the measured RSRP is less than a threshold.
[0145] Early indication may be configured by the gNB as a mandatory feature / function for RedCap UEs. In this case, it is mandatory for the RedCap UE to identify itself as a RedCap UE at an early stage (path B) during RACH processing, e.g., in Msg1, Msg3, or MsgA. Early indication may be used or configured for RedCap UEs when the size of the non-RedCap UL BWP is equal to or greater than the size of the UL BWP of the RedCap UE. The main reason for using early indication in this case is to provide more efficient resource allocation (or effective size of BWP) during RA processing for both RedCap and non-RedCap UEs (where non-RedCap UEs may use a wider BWP during RA process).
[0146] Msg3 repetition may also be available to RedCap UEs (per WID) with possible minor modifications as needed. The feature (Msg3 repetition) may be optional for RedCap UEs, even though it is likely to be useful for all RedCap UEs. To apply Msg3 repetition, the UE may need to use appropriate RACH resources to transmit Msg1. In one example, Msg1 may be used to indicate that the UE is a RedCap UE (early indication). Msg1 may be used to indicate that this CE feature applies (or Msg3 repetition is performed). In another example, Msg1 may be repeated and Msg3 may be used for early indication of RedCap.
[0147] If the gNB wants to support this CE feature (Msg3 Repetition) for all UE types (non-RedCap UE and RedCap UE), it may need to split the preamble / RO into 4 groups / areas: (RedCap, non-RedCap) x (Msg3 Repetition, non-Msg3 Repetition) (see Table 10 below).
[0148] [Table 10]
[0149] In the above Table 10, RACHi represents the i-th RACH configuration, and each RACH configuration may include one or more preambles, one or more ROs, or a combination thereof. The number of groups / areas is the number of RACH configurations. Each RACH configuration provides a configuration for the transmission of Msg1. According to Table 10, four RACH configurations may be configured, that is, RACH1 to RACH4 correspond to four different combinations of UE features, that is, RedCap UE and non-Msg3 repetition, RedCap UE and Msg3 repetition, non-RedCap UE and non-Msg3 repetition, and non-RedCap UE and Msg3 repetition, respectively.
[0150] However, the partitioning of resources may be too much to ask the UE to do, and therefore rules may need to be defined for the UE to decide which RACH configuration is to be used. Another problem is that the number of preamble and RACH resources is limited.
[0151] In the first embodiment, when early indication is not configured for RedCap UE, both RedCap UE and non-RedCap UE may use RO / preamble defined in CE feature with threshold. That is, when threshold is met (e.g., RSRP<threshold), both RedCap UE and non-RedCap UE may perform Msg3 coverage extension using defined RO / preamble. The same threshold may be used for RedCap UE and non-RedCap UE, or a separate threshold may be used for RedCap UE (e.g., when required to account for a feature that reduces complexity). As an example, UE (either RedCap or non-RedCap) may perform Msg3 repetition when RSRP measurement is less than a threshold. As another example, threshold 1 is configured for non-RedCap UE, and threshold 2 is configured for RedCap UE. In this case, a non-RedCap UE may perform Msg3 repetition when the RSRP measurement is less than threshold 1, and a RedCap UE may perform Msg3 repetition when the RSRP measurement is less than threshold 2. Table 11 below shows the RACH configurations of the first embodiment. As shown, two RACH configurations, RACH1 and RACH2, are needed corresponding to two categories, namely, UE with non-Msg3 repetition and UE with Msg3 repetition. When the UE's RSRP measurement is greater than the threshold, the UE transmits Msg1 according to RACH1 without performing Msg3 repetition. When the UE's RSRP measurement is less than the threshold, the UE transmits Msg1 according to RACH2 and performs Msg3 repetition.
[0152] [Table 11]
[0153] In some embodiments, a RedCap UE with certain characteristics (e.g., a RedCap UE with one Rx branch (or two Rx branches) in a band that requires four Rx branches for non-RedCap UEs) may be assigned to a non-repetitive region (e.g., a RedCap UE with two RXs) (i.e., RACH1 in Table 11) or may be assigned to a repetitive region (e.g., a RedCap UE with one Rx branch) (i.e., RACH2 in Table 11).
[0154] A combination of UE features and thresholds may also be used. For example, RedCap UEs and non-RedCap UEs with two Rx branches and RSRP higher than the threshold may use normal RO (i.e., RACH1), or RedCap UEs with one Rx branch and RSRP lower than the threshold may use CE RO (i.e., RACH2 in Table 11). The use of the repeat region (for Msg3) (i.e., RACH2 in Table 11) requires support of the CE feature by the UE.
[0155] Note that if this CE feature (Msg3 repetition) is mandatory for RedCap UEs, it may appear similar to a form of early indication by not being unique. For example, if Msg3 repetition is mandatory for RedCap UEs, the network knows that RedCap UEs support Msg3 repetition and RedCap UEs know that they can use Msg3 repetition (e.g., if conditions are met, as shown in Tables 10 and 11). Furthermore, the number of repetitions used for Msg3 may be used by the network to distinguish between RedCap UEs and non-RedCap UEs. Msg1 resources indicating CE may be requested by either RedCap or non-RedCap UEs. If the number of repetitions is unique for RedCap UEs and also for non-RedCap UEs, the base station may count the number of repetitions of Msg3 received to identify whether the message is from a RedCap UE or a non-RedCap UE. If the number of repetitions is not unique, the base station cannot use the number of repetitions to distinguish between RedCap UEs and non-RedCap UEs. As an example, a non-RedCap UE may use {1,2} repetitions, while a RedCap UE may use {4} repetitions to provide a form of early indication. The notation {x} is the allowed number of repetitions of Msg3. If there is a common value for the number of repetitions between non-RedCap UEs and RedCap UEs, for example, {1,2} is configured for non-RedCap UEs and {2,4} is configured for RedCap UEs, it may not be possible to distinguish the UE type when two Msg3 repetitions are received at the base station. That is, the base station may not know whether the two Msg3 repetitions are sent by a RedCap UE or a non-RedCap UE. There may not be a separate UL BWP for configured RedCap UEs. For example, both types of UE (RedCap and non-RedCap) share the same UL BWP, subject to constraints such as bandwidth and location, for the UL BWP for RedCap UE.
[0156] In the second embodiment, both early indication and Msg3 repetition features may be configured for RedCap UE, and non-RedCap UE and RedCap UE use the same region (same RACH configuration) for Msg3 repetition (so there are three regions (RACH1-3) in this example). Below, Table 12 shows the RACH configuration of the second embodiment. When Msg3 repetition is used, both non-RedCap UE and RedCap UE send Msg1 according to RACH2. When Msg3 repetition is not used, RedCap UE sends Msg1 according to RACH1, and non-RedCap UE sends Msg3 according to RACH3.
[0157] [Table 12]
[0158] In this example, the non-RedCap UE may send Msg3 repetitions in the same UL BWP as the RedCap UL BWP, since the RedCap UE and the non-RedCap UE use the "same RACH configuration" (e.g. poor channel condition because RSRP is less than a threshold), although it weakens the uniqueness of the early indication. The non-RedCap UE may still effectively send Msg3. As with the first embodiment described above, the threshold used to decide whether to perform Msg3 repetitions can be different for RedCap UEs and non-RedCap UEs. Using the number of repetitions to distinguish RedCap UEs of different characteristics (e.g. RedCap UEs with one Rx branch always use repetitions) is not possible, since in that case, embodiment 2 simplifies to embodiment 1. One limitation with this embodiment is that the RedCap and non-RedCap UEs share the same initial UL BWP during initial access, since the same RACH configuration (RACH2) is used by RedCap and non-RedCap UEs. Therefore, there may not be separate BWPs for RedCap UEs and non-RedCap UEs with repetition.
[0159] In the third embodiment, both early indication and CE feature of Msg3 repetition may be configured for RedCap UE, and non-RedCap and RedCap UEs use the same non-repetition region (RACH configuration) when Msg3 repetition is not performed, but use different regions (different RACH configurations) for repetition (so there are a total of three regions for this example). Table 12 below shows the RACH configuration according to the third embodiment. When Msg3 repetition is not used, both non-RedCap UE and RedCap UE transmit Msg1 according to RACH1. When Msg3 repetition is used, RedCap UE transmits Msg1 according to RACH2, and non-RedCap UE transmits Msg1 according to RACH4.
[0160] [Table 13]
[0161] The third embodiment may be less attractive, for example, a non-RedCap UE in good condition (e.g., RSRP is greater than the threshold, and therefore Msg3 repetition is not used) must follow the RedCap BW restriction (same RACH1). Also, if a RedCap UE does not support this CE feature of Msg3 repetition, it is treated the same as a non-RedCap UE according to the "same RACH configuration", regardless of its condition against the threshold or the supported features. The same embodiment as described in the first embodiment, e.g., threshold, may be applied. Potentially, this solution may allow a different number of repetitions for RedCap UEs and non-RedCap UEs (1, 2, 4 repetitions supported, and possibly 8 repetitions), since an early indication may be performed by the RedCap UE. This is reasonable since RedCap UEs have fewer branches, and the number of repetitions allowed for RedCap UEs may be greater than the number of repetitions configured for non-RedCap UEs. This may also be considered more attractive if a separate BWP for CE is used for RedCap and non-RedCap UEs for Msg3 transmission during initial access.
[0162] In the fourth embodiment, only RedCap UEs may be allowed to use the CE feature (so there may be two or three regions). The fourth embodiment may be similar to the second embodiment with three regions if the early indication (configured for RedCap UEs) is on and a) the CE feature is only signaled for RedCap UEs, or b) the threshold for CE is set to a value such that the CE feature is turned off for non-RedCap UEs and there is a RedCap threshold for RedCap UEs separate from non-RedCap UEs. Below, Table 14 shows the RACH configuration according to the fourth embodiment, where Msg3 repetition is generally turned off for non-RedCap UEs with an appropriate threshold value. When Msg3 repetition is not used, RedCap UEs transmit Msg1 according to RACH1, and non-RedCap UEs transmit Msg1 according to RACH3. When Msg3 repetition is used, RedCap UEs transmit Msg1 according to RACH2. Non-RedCap UEs can be configured with a very low threshold so that Msg3 repetition is not performed by non-RedCap UEs and non-RedCap UEs transmit Msg1 according to RACH3. RedCap UEs are configured with a different threshold (for performing Msg3 repetition) than the threshold configured for non-RedCap UEs. Once the three regions are configured, there is no problem with using a separate BWP for RedCap UEs (early indication is supported). Non-RedCap UEs do not use CE (or the network determines that it does not support CE for non-RedCap UEs).
[0163] [Table 14]
[0164] If there is no early indication configured for RedCap UE, there are two regions (RACH configuration). This example may be similar to the first embodiment, where a) the CE feature is only signaled for RedCap UE, or b) the threshold for CE is set to a value such that the CE feature is turned off for non-RedCap UE and there is a separate threshold for RedCap from non-RedCap UE. This example is shown below in Table 15. When Msg3 repetition is not used, RedCap UE and non-RedCap UE transmit Msg1 according to RACH1. When Msg3 repetition is used, RedCap UE transmits Msg1 according to RACH2. Non-RedCap UE may be configured with a very low threshold, such that Msg3 repetition is not performed by non-RedCap UE, resulting in non-RedCap UE transmitting Msg1 according to RACH1. RedCap UE is configured with a threshold (for performing Msg3 repetition) different from the threshold configured for non-RedCap UE.
[0165] [Table 15]
[0166] FIG. 9 is a flow diagram of an embodiment method 900 for RedCap UE indication. Method 900 may illustrate the operation of a UE. The UE may determine whether to indicate to the gNB that it is a reduced capability (RedCap) UE during or after a random access (RA) procedure of the UE based on a criterion (block 902). A RedCap UE has a quantity of receiving branches less than the minimum number of receiving branches of a non-RedCap UE or has a bandwidth less than the minimum bandwidth of a non-RedCap UE. The UE may indicate to the gNB that it is a RedCap UE according to the determination result (block 904). A non-RedCap UE may be a legacy UE.
[0167] FIG. 10 is a flow diagram of another embodiment method 1000 for RedCap UE detection. Method 1000 may illustrate operation of a gNB. The gNB may receive a first message from a UE during a random access (RA) procedure (block 1002). The gNB may determine whether the first message indicates that the UE is a reduced capability (RedCap) UE (block 1004). A RedCap UE has a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE or has a bandwidth less than a minimum bandwidth of a non-RedCap UE. When the first message indicates that the UE is a RedCap UE, the gNB may send a second message to the UE during the RA procedure according to a coverage restoration technique (block 1006). When the first message does not indicate that the UE is a RedCap UE, the gNB may determine whether the UE is a RedCap UE after the RA procedure is completed (block 1008).
[0168] FIG. 11 illustrates a block diagram of an embodiment of a processing system 1100 for performing the methods described herein that may be installed in a host device. As illustrated, the processing system 1100 includes a processor 1104, a memory 1106, and interfaces 1110-1114, which may (or may not) be arranged as shown in FIG. 11. The processor 1104 may be any component or collection of components adapted to perform tasks associated with computation and / or other processing, and the memory 1106 may be any component or collection of components adapted to store programming and / or instructions for execution by the processor 1104. In one embodiment, the memory 1106 includes a non-transitory computer-readable medium. The interfaces 1110, 1112, 1114 may be any component or collection of components that enable the processing system 1100 to communicate with other devices / components and / or users. For example, one or more of the interfaces 1110, 1112, 1114 may be adapted to communicate data, control, or management messages from the processor 1104 to applications installed on the host device and / or remote devices. As another example, one or more of the interfaces 1110, 1112, 1114 may be adapted to allow a user or a user device (e.g., a personal computer (PC), etc.) to interact / communicate with the processing system 1100. The processing system 1100 may include additional components not shown in FIG. 11 , such as long-term storage (e.g., non-volatile memory, etc.).
[0169] In some embodiments, the processing system 1100 is included in a network device that is accessing or otherwise part of a telecommunications network. In one example, the processing system 1100 is in a network-side device in a wireless or wired telecommunications network, such as a base station, a relay station, a scheduler, a controller, a gateway, a router, an application server, or any other device in a telecommunications network. In other embodiments, the processing system 1100 is in a user-side device that accesses a wireless or wired telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communication device (e.g., a smart watch, etc.), or any other device adapted to access a telecommunications network.
[0170] In some embodiments, one or more of the interfaces 1110, 1112, 1114 connect the processing system 1100 to a transceiver adapted to transmit and receive signaling over a telecommunications network. FIG. 12 shows a block diagram of a transceiver 1200 adapted to transmit and receive signaling over a telecommunications network. The transceiver 1200 may be installed in a host device. As shown, the transceiver 1200 comprises a network-side interface 1202, a coupler 1204, a transmitter 1206, a receiver 1208, a signal processor 1210, and a device-side interface 1212. The network-side interface 1202 may include any component or collection of components adapted to transmit or receive signaling over a wireless or wired telecommunications network. The coupler 1204 may include any component or collection of components adapted to facilitate bidirectional communication over the network-side interface 1202. The transmitter 1206 may include any component or collection of components (e.g., upconverter, power amplifier, etc.) adapted to convert a baseband signal to a modulated carrier signal suitable for transmission via the network-side interface 1202. The receiver 1208 may include any component or collection of components (e.g., downconverter, low noise amplifier, etc.) adapted to convert a carrier signal received via the network-side interface 1202 to a baseband signal. The signal processor 1210 may include any component or collection of components adapted to convert a baseband signal to a data signal suitable for communication via the device-side interface 1212, or vice versa. The device-side interface 1212 may include any component or collection of components adapted to communicate data signals between the signal processor 1210 and components within the host device (e.g., processing system 1100, local area network (LAN) port, etc.).
[0171] The transceiver 1200 may transmit and receive signaling over any type of communication medium. In some embodiments, the transceiver 1200 transmits and receives signaling over a wireless medium. For example, the transceiver 1200 may be a wireless transceiver adapted to communicate according to a wireless telecommunications protocol, such as a cellular protocol (e.g., Long Term Evolution (LTE), etc.), a Wireless Local Area Network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, Near Field Communication (NFC), etc.). In such an embodiment, the network-side interface 1202 comprises one or more antennas / radiating elements. For example, the network-side interface 1202 may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-tier communication, e.g., single-input multiple-output (SIMO), multiple-input single-output (MISO), multiple-input multiple-output (MIMO), etc. In other embodiments, the transceiver 1200 transmits and receives signaling over a wired medium, e.g., twisted pair cable, coaxial cable, fiber optics, etc. A particular processing system and / or transceiver may utilize all of the components shown, or only a subset of the components, and the level of integration may vary from device to device.
[0172] 13 is a block diagram of an electronic device (ED) 1352 shown in a computing and communication environment 1300 that may be used to implement the devices and methods disclosed herein. Examples of EDs include UEs, tablets, IoT devices, computers, or other devices with wireless communication capabilities.
[0173] In some embodiments, the electronic device may be an element of a communications network infrastructure, such as a base station (e.g., a NodeB, evolved NodeB (eNodeB, or eNB), a next generation NodeB (sometimes referred to as a gNodeB or gNB), a home subscriber server (HSS), a gateway (GW) such as a packet gateway (PGW) or a serving gateway (SGW), or various other nodes or functions in a core network (CN) or a public land mobility network (PLMN). In other embodiments, the electronic device may be a device that connects to the network infrastructure over a radio interface, such as a mobile phone, a smartphone, or other such device that may be classified as a user equipment (UE). In some embodiments, the ED 1352 may be a machine type communication (MTC) device (also referred to as a machine-to-machine (m2m) device), or another such device that may be classified as a UE even though it does not directly provide services to a user. In some references, the ED may be , or mobile device, the term intended to reflect a device that connects to a mobile network, whether the device itself is designed for or capable of mobility. A particular device may utilize all of the components shown, or only a subset of the components, and the level of integration may vary from device to device. Additionally, a device may include multiple instances of components, such as multiple processors, memory, transmitters, receivers, etc. The ED 1352 typically includes a processor 1354, such as a central processing unit (CPU), and may further include a specialized processor, such as a graphics processing unit (GPU) or other such processor, memory 1356, a network interface 1358, and a bus 1360 for connecting the components of the ED 1352. The ED 1352 may optionally include components such as a mass storage device 1362 (shown in dashed lines), a video adapter 1364, and an I / O interface 1368.
[0174] Memory 1356 may comprise any type of non-transitory system memory readable by processor 1354, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read only memory (ROM), or a combination thereof. In one embodiment, memory 1356 may include more than one type of memory, such as ROM for use during boot-up and DRAM for storing programs and data for use while executing programs. Bus 1360 may be one or more of any type of several bus architectures, including a memory bus or memory controller, a peripheral bus, or a video bus.
[0175] The electronic device 1352 may include one or more network interfaces 1358, which may include at least one of a wired network interface and a wireless network interface. As shown in FIG. 13, the network interface 1358 may include a wired network interface for connecting to a network 1374 and may include a radio access network interface 1372 for connecting to other devices via a wireless link. When the ED 1352 is a network infrastructure element, the radio access network interface 1372 may be omitted for nodes or functions that serve as elements of a PLMN other than those at the radio edge (e.g., eNBs). When the ED 1352 is an infrastructure at the radio edge of a network, both a wired network interface and a wireless network interface may be included. When the ED 1352 is a wirelessly connected device such as a user equipment, the radio access network interface 1372 may be present, which may be supplemented by other wireless interfaces such as a WiFi network interface. The network interface 1358 enables the ED 1352 to communicate with remote entities, such as those connected to the network 1374.
[0176] Mass storage 1362 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via bus 1360. Mass storage 1362 may comprise, for example, one or more of a solid state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive. In some embodiments, mass storage 1362 may be remote to electronic device 1352 and accessible by using a network interface, such as interface 1358. In the illustrated embodiment, mass storage 1362 is separate from memory 1356, in which it is included, and may generally perform storage tasks compatible with higher latency, but may generally provide less volatility or no volatility at all. In some embodiments, mass storage 1362 may be integrated with disparate memory 1356.
[0177] Optional video adapter 1364 (shown in dashed lines) and I / O interface 1368 provide interfaces for coupling electronic device 1352 to external input and output devices. Examples of input and output devices include a display 1366 coupled to video adapter 1364 and an I / O device 1370, such as a touch screen, coupled to I / O interface 1368. Other devices may be coupled to ED 1352 and additional or fewer interfaces may be utilized. For example, a serial interface such as a universal serial bus (USB) (not shown) may be used to provide an interface for external devices. Those skilled in the art will appreciate that in embodiments in which ED 1352 is part of a data center, I / O interface 1368 and video adapter 1364 may be virtualized and provided through network interface 1358.
[0178] In some embodiments, the ED 1352 may be an independent device, while in other embodiments, the electronic device 1352 may reside within a data center. A data center, as understood in the art, is a collection of computing resources (typically in the form of servers) that can be used as a collective computing and storage resource. Within a data center, multiple servers can be connected to each other, thereby providing a computing resource pool in which virtualized entities can be instantiated. Data centers can be interconnected to each other to form a network of pooled computing and storage resources connected to each other by connectivity resources. The connectivity resources can take the form of physical connections, such as Ethernet or optical communication links, and in some cases, can also include wireless communication channels. When two different data centers are connected by multiple different communication channels, the links can be combined together using any of a number of techniques, including the formation of a link aggregation group (LAG). It should be understood that any or all of the computing resources, storage resources, and connectivity resources (along with other resources in the network) can be divided among different sub-networks, possibly in the form of resource slices. Different network slices can be created when resources across a collection of several connected data centers or other nodes are sliced.
[0179] It should be understood that one or more steps of the method of the embodiments provided herein may be performed by a corresponding unit or module. For example, the signal may be transmitted by a transmitting unit or a transmitting module. The signal may be received by a receiving unit or a receiving module. The signal may be processed by a processing unit or a processing module. Other steps may be performed by a determining unit / module, a RedCap UE indicating or identifying unit / module, a comparing unit / module, a measuring unit / module, a function exchanging unit / module, a RACH configuration unit / module, a broadcast coverage recovery, a RACH executing unit / module, a receive coverage recovery unit / module, and / or a coverage recovery unit / module. Each unit / module may be hardware, software, or a combination thereof. For example, one or more of the units / modules may be an integrated circuit, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The following references are relevant to the subject matter of this disclosure and are incorporated herein by reference in their entirety:
[0180] · Ericsson, “Revised SID on Study on Support of Reduced Capability NR Devices”, document RP-201677, 3GPP, Jul.2020;
[0181] · TR38.875,v0.1.0 “Study on Support of Reduced Capability NR Devices” (Release 17), 2020-11-25; · TS36.300,v16.3.0,"E-UTRA E-UTRAN Overall Description Stage-2";
[0182] · TS38.331,v16.2.0,"Radio Resource RRC protocol specification",(Release 16);
[0183] · TS36.331,V13.11.0,"Radio Resource RRC protocol specification",(Release 13),2018-09-27;
[0184] · TS38.300,V16.3.0,"NR and NG-RAN Overall description;Stage-2",(Release 16),2020-10-02;
[0185] · TS36.213,V13.11.0,"Evolved Universal Terrestrial Radio Access(E-UTRA);Physical layer procedures",(Release 13),2018-10-01;
[0186] · TS38.306,V16-2, “User Equipment (UE) radio access capabilities”, (Release 16), 2020-10-02
[0187] Although the description has been given in detail, it should be understood that various changes, substitutions, and alterations can be made thereto without departing from the spirit and scope of the present disclosure, as defined by the appended claims. Moreover, the scope of the present disclosure is not limited to the specific embodiments described herein, and those skilled in the art will readily appreciate from this disclosure that currently existing or later developed processes, machines, manufactures, compositions of matter, means, methods, or steps may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. It is therefore intended that the appended claims include within their scope such processes, machines, manufactures, compositions of matter, means, methods, or steps.
Claims
1. determining, by a user equipment (UE), whether to indicate to a gNB during a random access (RA) procedure that the UE is a reduced capability (RedCap) UE, or whether to indicate to the gNB after the RA procedure that the UE is a RedCap UE based on a criterion, the RedCap UE having a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE, or having a bandwidth less than a minimum bandwidth of the non-RedCap UE, the criterion being related to a number of receiving branches of the UE, a reference signal received power (RSRP) measured by the UE, a reference signal received quality (RSRQ) measured by the UE, a reference signal strength indicator (RSSI) measured by the UE, a combination thereof, or a capability of the UE; indicating, by the UE, to the gNB, that the UE is the RedCap UE according to the determination result; A method comprising:
2. The non-RedCap UE is a legacy UE. The method of claim 1.
3. The RedCap UE has one or two receiving branches. The method according to claim 1 or 2.
4. The minimum number of receive branches for the non-RedCap UE is 4 for Frequency Range 1 (FR1) and 2 for Frequency Range 2 (FR2). The method according to any one of claims 1 to 3.
5. The steps of the present invention are as follows: The method includes sending, by the UE, a first message indicating the UE as the RedCap UE during the RA procedure to the gNB when the UE determines to indicate the UE as the RedCap UE during the RA procedure, the first message including a message 1 (Msg1) of the RA procedure, a message 3 (Msg3) of the RA procedure, or a message A (MsgA) of the RA procedure. The method according to any one of claims 1 to 4.
6. and determining, by the UE, the first message before the RA procedure based on a radio resource control (RRC) configuration broadcast by the gNB and received by the UE before the RA procedure. The method according to claim 5.
7. The RRC configuration includes information of the criteria. The method according to claim 6.
8. The first message is sent by the UE according to a physical random access channel (PRACH) configuration broadcast by the gNB and received by the UE before the RA procedure, the PRACH configuration including a RACH preamble, a RACH occasion, or a combination thereof, which is related to indicating a RedCap UE; The method according to any one of claims 5 to 7.
9. Further comprising receiving, by the UE, a message 2 (Msg2) or a message 4 (Msg4) from the gNB during the RA procedure according to a received coverage recovery technique. The method according to any one of claims 5 to 8.
10. the first message is the Msg1, and the method further comprises: The method further includes repeating the transmission of the Msg3 to the gNB by the UE. The method according to any one of claims 5 to 9.
11. The number of repetitions of the transmission of the Msg3 follows the RACH configuration The method of claim 10.
12. The step of repeating the transmission of the Msg3 is performed when a Reference Signal Received Power (RSRP) measurement of the UE is less than a threshold. The method of claim 10.
13. The steps of the present invention are as follows: The UE includes a step of sending, to the gNB, information of a UE capability indicating the UE as the RedCap UE after the RA procedure is completed when the UE determines to indicate the UE as the RedCap UE after the RA procedure is completed. The method according to any one of claims 1 to 4.
14. The determining step includes: determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the UE has two receiving branches; or determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has one receiving branch; Includes The method according to any one of claims 1 to 13.
15. The determining step includes: determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the UE has two receiving branches and is capable of operating in Frequency Range 1 (FR1) or FR2; determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has one receiving branch and is operable in FR1 or FR2; or determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has two receiving branches and is operable in FR1; Includes The method according to any one of claims 1 to 13.
16. The determining step includes: comparing, by the UE, the RSRP measurement with a threshold configured for RedCap UE; determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the RSRP measurement is greater than the threshold; or determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the RSRP measurement of the UE is below the threshold. Includes The method according to any one of claims 1 to 13.
17. The determining step includes: comparing, by the UE, the RSRP measurement with a threshold configured for RedCap UE; determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the UE has two receive branches and the RSRP measurement is greater than the threshold; determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has two receive branches and the RSRP measurement of the UE is below the threshold; or determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has one receiving branch; Includes The method according to any one of claims 1 to 13.
18. The determining step includes: comparing, by the UE, the RSRP measurement with a threshold configured for RedCap UE; determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the UE has one receive branch and the RSRP measurement is greater than the threshold; determining, by the UE, to indicate the UE as the RedCap UE during the RA procedure when the UE has one receive branch and the RSRP measurement is below the threshold; or determining, by the UE, to indicate the UE as the RedCap UE after the RA procedure when the UE has two receiving branches; Includes The method according to any one of claims 1 to 13.
19. 1. A method comprising: Receiving, by the gNB, a first message from a user equipment (UE) during a random access (RA) procedure; determining, by the gNB, whether the first message indicates the UE as a reduced capability (RedCap) UE, the RedCap UE having a quantity of receive branches less than a minimum number of receive branches of a non-RedCap UE or having a bandwidth less than a minimum bandwidth of the non-RedCap UE; When the first message indicates the UE as the RedCap UE, sending a second message by the gNB to the UE during the RA procedure according to a coverage restoration technique; When the first message does not indicate the UE as the RedCap UE, determining, by the gNB, whether the UE is the RedCap UE after the RA procedure is completed; A method comprising:
20. The non-RedCap UE is a legacy UE.
20. The method of claim 19.
21. The RedCap UE has one or two receiving branches.
21. The method according to claim 19 or 20.
22. The minimum number of receive branches for the non-RedCap UE is 4 for Frequency Range 1 (FR1) and 2 for Frequency Range 2 (FR2). The method according to any one of claims 19 to 21.
23. The first message includes a message 1 (Msg1) of the RA procedure, a message 3 (Msg3) of the RA procedure, or a message A (MsgA) of the RA procedure. The method according to any one of claims 19 to 22.
24. The first message is based on a physical random access channel (PRACH) configuration broadcast by the gNB, the PRACH configuration including a RACH preamble, a RACH occasion, or a combination thereof, which is related to indicating a RedCap UE.
24. The method of claim 23.
25. The second message is message 2 (Msg2) of the RA procedure or message 4 (Msg4) of the RA procedure. The method according to any one of claims 19 to 24.
26. The gNB further includes receiving, from the UE, UE capability information indicating the UE as the RedCap UE after the RA procedure is completed. The method according to any one of claims 19 to 23.
27. The method further includes a step of broadcasting criteria information to the UE by the gNB, enabling the UE to decide whether to indicate the UE as the RedCap UE to the gNB during or after the RA procedure based on the criteria. The method according to any one of claims 19 to 26.
28. The criterion may be based on a number of receive branches of the UE, a Reference Signal Received Power (RSRP) measurement of the UE, a Reference Signal Received Quality (RSRQ) measurement of the UE, a Reference Signal Strength Indicator (RSSI) of the UE, or a combination thereof.
28. The method of claim 27.
29. The criteria are based on the capabilities of the UE.
29. The method of claim 27 or 28.
30. The criteria are: indicating the RedCap UE after the RA procedure when the UE has two receiving branches; or indicating the RedCap UE during the RA procedure when the UE has one receiving branch. Includes 30. The method according to any one of claims 27 to 29.
31. The criteria are: indicating the RedCap UE after the RA procedure when the UE has two receiving branches and is capable of operating in Frequency Range 1 (FR1) or FR2; indicating the RedCap UE during the RA procedure when the UE has one receiving branch and is operable in FR1 or FR2; or indicating the RedCap UE during the RA procedure when the UE has two receiving branches and is operational in FR1. Includes 30. The method according to any one of claims 27 to 29.
32. The criteria are: indicating the RedCap UE after the RA procedure when the RSRP measured by the UE is greater than a threshold; or indicating the RedCap UE during the RA procedure when the RSRP measured by the UE is less than or equal to the threshold. Includes 30. The method according to any one of claims 27 to 29.
33. The criteria are: indicating the RedCap UE after the RA procedure when the UE has two receiving branches and the RSRP measured by the UE is greater than a threshold; indicating the RedCap UE during the RA procedure when the UE has two receiving branches and the RSRP measured by the UE is below the threshold; or indicating the RedCap UE during the RA procedure when the UE has one receiving branch. Includes 30. The method according to any one of claims 27 to 29.
34. The criteria are: indicating the RedCap UE after the RA procedure when the UE has one receiving branch and the RSRP measured by the UE is greater than a threshold; indicating the RedCap UE during the RA procedure when the UE has one receiving branch and the RSRP measured by the UE is less than or equal to the threshold; or indicating the RedCap UE after the RA procedure when the UE has two receiving branches. Includes 30. The method according to any one of claims 27 to 29.
35. Further comprising broadcasting, by the gNB, information indicating that the gNB supports RedCap UE. The method according to any one of claims 19 to 34.
36. a non-transitory memory storage having instructions; one or more processors in communication with the memory storage; wherein the instructions, when executed by the one or more processors, cause the apparatus to: Determining whether the device indicates to the gNB that it is a reduced capability (RedCap) UE during a random access (RA) procedure of the device, or indicates to the gNB that the device is a RedCap UE after the RA procedure based on a criterion, the RedCap UE having a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE, or having a bandwidth less than a minimum bandwidth of the non-RedCap UE, the criterion being related to a number of receiving branches of the UE, a reference signal received power (RSRP) measured by the UE, a reference signal received quality (RSRQ) measured by the UE, a reference signal strength indicator (RSSI) measured by the UE, a combination thereof, or a capability of the UE; Indicating to the gNB that the device is the RedCap UE according to the determination result; A device that performs the above.
37. a non-transitory memory storage having instructions; one or more processors in communication with the memory storage; wherein the instructions, when executed by the one or more processors, cause the apparatus to: Receiving a first message from a user equipment (UE) during a random access (RA) procedure; determining whether the first message indicates the UE as a reduced capability (RedCap) UE, the RedCap UE having a quantity of receive branches less than a minimum number of receive branches of a non-RedCap UE or having a bandwidth less than a minimum bandwidth of the non-RedCap UE; sending a second message to the UE during the RA procedure according to a coverage restoration technique when the first message indicates the UE as the RedCap UE; determining whether the UE is the RedCap UE after the RA procedure is completed when the first message does not indicate the UE as the RedCap UE; A device that performs the above.
38. A non-transitory computer-readable medium storing computer instructions that, when executed by one or more processors of a device, cause the device to: Determining whether the device indicates to the gNB that it is a reduced capability (RedCap) UE during a random access (RA) procedure of the device, or indicates to the gNB that the device is a RedCap UE after the RA procedure based on a criterion, the RedCap UE having a quantity of receiving branches less than a minimum number of receiving branches of a non-RedCap UE, or having a bandwidth less than a minimum bandwidth of the non-RedCap UE, the criterion being related to a number of receiving branches of the UE, a reference signal received power (RSRP) measured by the UE, a reference signal received quality (RSRQ) measured by the UE, a reference signal strength indicator (RSSI) measured by the UE, a combination thereof, or a capability of the UE; Indicating to the gNB that the device is the RedCap UE according to the determination result; A non-transitory computer-readable medium for causing the computer to execute
39. A non-transitory computer-readable medium storing computer instructions that, when executed by one or more processors of a device, cause the device to: Receiving a first message from a user equipment (UE) during a random access (RA) procedure; determining whether the first message indicates the UE as a reduced capability (RedCap) UE, the RedCap UE having a quantity of receive branches less than a minimum number of receive branches of a non-RedCap UE or having a bandwidth less than a minimum bandwidth of the non-RedCap UE; sending a second message to the UE during the RA procedure according to a coverage restoration technique when the first message indicates the UE as the RedCap UE; determining whether the UE is the RedCap UE after the RA procedure is completed when the first message does not indicate the UE as the RedCap UE; A non-transitory computer-readable medium for causing the computer to execute
40. A system comprising a user equipment (UE) and a gNB, The UE, Determining whether the UE indicates to the gNB that it is a reduced capability (RedCap) UE during a random access (RA) procedure of the UE or indicates to the gNB that it is a RedCap UE after the RA procedure based on a criterion, wherein the RedCap UE has a quantity of receiving branches that is less than a minimum number of receiving branches of a non-RedCap UE or has a bandwidth that is less than a minimum bandwidth of the non-RedCap UE; According to the determination result, indicating to the gNB that the UE is the RedCap UE; configured to run The gNB is receiving a first message from the UE during a random access (RA) procedure; determining whether the first message indicates the UE as the RedCap UE; sending a second message to the UE during the RA procedure according to a coverage restoration technique when the first message indicates the UE as the RedCap UE; determining whether the UE is the RedCap UE after the RA procedure is completed when the first message does not indicate the UE as the RedCap UE; A system configured to run
Citation Information
Patent Citations
Information transmission method, device, and storage medium
JP2023549010A
Early indication of reduced capability device
US20230030240A1
Information transmission method, devices, and storage medium
WO2022061507A1
