IP Library › Granted Patent US 12,363,701
Granted Patent B2
US 12,363,701 · App. 18/656,955 · Granted Jul 15, 2025

Method for determining frequency domain location of control resource set and related device

Inventors: Fei Gao (Shanghai, CN); Shujing Yu (Beijing, CN); Xu Zhang (Beijing, CN); Weihua Li (Shenzhen, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W72/1263H04L1/1896H04W72/0453H04W72/0466H04W72/20H04W72/23H04W72/53
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,363,701
App. No.
18/656,955
Granted
Jul 15, 2025
Kind
B2
Abstract

A common CORESET determining method, an apparatus and a non-transitory computer-readable storage medium are provided. The method includes: receiving configuration information, wherein the configuration information indicates where a physical resource block occupied by a first common control resource set is located in a first downlink bandwidth part; determining a frequency domain resource of the first common control resource set based on a frequency domain resource of the first downlink bandwidth part and the physical resource block occupied by the first common control resource set within the first downlink bandwidth part; and monitoring a physical downlink control channel in the first common control resource set before the first downlink bandwidth part configured by a SIB1 takes effect to obtain scheduling control information. According to this application, complexity of determining a frequency domain location of the first control resource set can be reduced.

Claims (51)

1. A method, comprising:

receiving, by an apparatus, configuration information of a first common control resource set before successful initial access of the apparatus, wherein the configuration information indicates where a physical resource block occupied by the first common control resource set is located in a first downlink bandwidth part, and wherein the first downlink bandwidth part is configured by system information block 1 (SIB1) and takes effect after the successful initial access of the apparatus; and

monitoring, by the apparatus, a physical downlink control channel in the first common control resource set before the successful initial access of the apparatus, to obtain uplink scheduling control information or downlink scheduling control information, wherein

a start common resource block of the first common control resource set is determined based on a start common resource block of the first downlink bandwidth part and the configuration information of the first common control resource set.

2. The method according to claim 1 , wherein the first downlink bandwidth part is different from an initial downlink bandwidth part defined by control resource set 0 (CORESET #0).

3. The method according to claim 2 , wherein the initial downlink bandwidth part defined by CORESET #0 takes effect before successful initial access of a terminal device.

4. The method according to claim 3 , wherein the successful initial access of the apparatus indicates one of the following occasions:

an occasion on which the apparatus successfully receives an initially transmitted message 4 and sends an acknowledgement message to a network device;

an occasion on which the apparatus successfully receives, after the apparatus successfully receives an initially transmitted message 4, downlink control information (DCI) scrambled by a cell radio network temporary identifier (C-RNTI);

an occasion on which the apparatus successfully receives a retransmitted message 4 and sends an acknowledgement message to a network device;

an occasion on which the apparatus successfully receives, after the apparatus successfully receives a retransmitted message 4, DCI scrambled by a C-RNTI;

an occasion on which the apparatus successfully receives, after successfully receiving an initially transmitted message 4, configuration information indicating that DCI scrambled by a C-RNTI needs to be blindly detected;

an occasion on which the apparatus successfully receives, after successfully receiving a retransmitted message 4, configuration information indicating that DCI scrambled by a C-RNTI needs to be blindly detected; or

an occasion on which the apparatus switches from the initial downlink bandwidth part defined by using CORESET #0 to the first downlink bandwidth part configured by the SIB1 after successfully receiving an initially transmitted message 4 or a retransmitted message 4.

5. The method according to claim 1 , further comprising:

monitoring, by the apparatus, a physical downlink control channel in the first common control resource set after the successful initial access of the apparatus, to obtain uplink scheduling control information or downlink scheduling control information.

6. The method according to claim 1 , wherein an identifier of the first common control resource set is not 0.

7. The method according to claim 1 , wherein the uplink scheduling control information or downlink scheduling control information may be control information for scheduling a random access response, control information for scheduling a paging message, or control information for scheduling a system message.

8. An apparatus, comprising:

one or more processors configured to:

receive configuration information of a first common control resource set before successful initial access of the apparatus, wherein the configuration information indicates where a physical resource block occupied by the first common control resource set is located in a first downlink bandwidth part, and wherein the first downlink bandwidth part is configured by system information block 1 (SIB1) and takes effect after the successful initial access of the apparatus; and

monitor a physical downlink control channel in the first common control resource set before the successful initial access of the apparatus, to obtain uplink scheduling control information or downlink scheduling control information, wherein

a start common resource block of the first common control resource set is determined based on a start common resource block of the first downlink bandwidth part and the configuration information of the first common control resource set.

9. The apparatus according to claim 8 , wherein the first downlink bandwidth part is different from an initial downlink bandwidth part defined by control resource set 0 (CORESET #0).

10. The apparatus according to claim 9 , wherein the initial downlink bandwidth part defined by CORESET #0 takes effect before successful initial access of the apparatus.

11. The apparatus according to claim 8 , wherein the successful initial access of the apparatus indicates one of the following occasions:

an occasion on which the apparatus successfully receives an initially transmitted message 4 and sends an acknowledgement message to a network device;

an occasion on which the apparatus successfully receives, after the apparatus successfully receives an initially transmitted message 4, downlink control information (DCI) scrambled by a cell radio network temporary identifier (C-RNTI);

an occasion on which the apparatus successfully receives a retransmitted message 4 and sends an acknowledgement message to a network device;

an occasion on which the apparatus successfully receives, after the apparatus successfully receives a retransmitted message 4, DCI scrambled by a C-RNTI;

an occasion on which the apparatus successfully receives, after successfully receiving an initially transmitted message 4, configuration information indicating that DCI scrambled by a C-RNTI needs to be blindly detected;

an occasion on which the apparatus successfully receives, after successfully receiving a retransmitted message 4, configuration information indicating that DCI scrambled by a C-RNTI needs to be blindly detected; or

an occasion on which the apparatus switches from an initial downlink bandwidth part defined by using CORESET #0 to the first downlink bandwidth part configured by the SIB1 after successfully receiving an initially transmitted message 4 or a retransmitted message 4.

12. The apparatus according to claim 8 , wherein the one or more processors further configured to:

monitor a physical downlink control channel in the first common control resource set after the successful initial access of the apparatus, to obtain uplink scheduling control information or downlink scheduling control information.

13. The apparatus according to claim 8 , wherein the uplink scheduling control information or downlink scheduling control information may be control information for scheduling a random access response, control information for scheduling a paging message, or control information for scheduling a system message.

14. A method, comprising:

sending, by an apparatus, configuration information of a first common control resource set before successful initial access of a terminal device, wherein the configuration information indicates where a physical resource block occupied by the first common control resource set is located in a first downlink bandwidth part, and wherein the first downlink bandwidth part is configured by system information block 1 (SIB1) and takes effect after the successful initial access of the terminal device; and

sending, by the apparatus, uplink scheduling control information or downlink scheduling control information on a physical downlink control channel in the first common control resource set before the successful initial access of the terminal device.

15. The method according to claim 14 , wherein the first downlink bandwidth part is different from an initial downlink bandwidth part defined by control resource set 0 (CORESET #0).

16. The method according to claim 15 , wherein the initial downlink bandwidth part defined by CORESET #0 takes effect before successful initial access of the terminal device.

17. The method according to claim 14 , wherein a start common resource block of the first common control resource set is determined based on a start common resource block of the first downlink bandwidth part and the configuration information of the first common control resource set.

18. The method according to claim 14 , wherein the successful initial access of the terminal device is used to indicate one of the following occasions:

an occasion on which the apparatus receives an acknowledgement message that is sent by the terminal device and that is for an initially transmitted message 4 sent by the apparatus;

an occasion on which the apparatus receives an acknowledgement message that is sent by the terminal device and that is for a retransmitted message 4 sent by the apparatus;

an occasion on which the apparatus sends, to the terminal device after receiving an acknowledgement message that is sent by the terminal device and that is for an initially transmitted message 4 sent by the apparatus, configuration information used to indicate that DCI scrambled by using a C-RNTI needs to be blindly detected;

an occasion on which the apparatus sends, to the terminal device after receiving an acknowledgement message that is sent by the terminal device and that is for a retransmitted message 4 sent by the apparatus, configuration information used to indicate that DCI scrambled by using a C-RNTI needs to be blindly detected; or

an occasion on which the terminal device switches from an initial downlink bandwidth part defined by using CORESET #0 to the first downlink bandwidth part configured by the SIB1 after successfully receiving an initially transmitted message 4 or a retransmitted message 4.

19. The method according to claim 14 , further comprising:

sending, by the apparatus, uplink scheduling control information or downlink scheduling control information on a physical downlink control channel in the first common control resource set after the successful initial access of the terminal device.

20. The method according to claim 14 , wherein the uplink scheduling control information or downlink scheduling control information may be control information for scheduling a random access response, control information for scheduling a paging message, or control information for scheduling a system message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 19, 2024
From: GAO, FEI; YU, SHUJING; ZHANG, XU; LI, WEIHUA
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 068029/0915 →
Priority Claims (1)
CN 201811642765.X · Dec 29, 2018 · national
Continuity (3)
Continuation 17360347 · Jun 28, 2021
Continuation PCTCN2019128916 · Dec 26, 2019
Related Publication 20240365308A1 · Oct 31, 2024
References Cited (37)
US 20180192383A1 · Nam et al. · 2018 [cited by applicant]
US 20180279289A1 · Islam et al. · 2018 [cited by applicant]
US 20190349060A1 · Liao et al. · 2019 [cited by applicant]
US 20200196285A1 · Zhuang · 2020 [cited by examiner]
US 20200252180A1 · Takeda · 2020 [cited by examiner]
US 20200344034A1 · Moon et al. · 2020 [cited by applicant]
US 20210092772A1 · Nakashima · 2021 [cited by examiner]
US 20210185679A1 · Yoshimura et al. · 2021 [cited by applicant]
US 20210227558A1 · Matsumura et al. · 2021 [cited by applicant]
CN 102238750A · 2011 [cited by applicant]
CN 105934980A · 2016 [cited by applicant]
CN 108365928A · 2018 [cited by applicant]
CN 108401526A · 2018 [cited by applicant]
CN 108631934A · 2018 [cited by applicant]
CN 108737050A · 2018 [cited by applicant]
CN 108882376A · 2018 [cited by applicant]
WO 2018059391A1 · 2018 [cited by applicant]
3GPP TS 38.211 V15.3.0 (Sep. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 15),” Sep. 2018, 96 pages. [cited by applicant]
3GPP TS 38.212 V15.3.0 (Sep. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR;Multiplexing and channel coding (Release 15),” Sep. 2018, 99 pages. [cited by applicant]
3GPP TS 38.213 V15.3.0 (Sep. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15),” Sep. 2018, 101 pages. [cited by applicant]
3GPP TS 38.214 V15.3.0 (Sep. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15),” Sep. 2018, 96 pages. [cited by applicant]
3GPP TS 38.300 V15.3.1 (Oct. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15),” Oct. 2018, 92 pages. [cited by applicant]
3GPP TS 38.331 V15.3.0 (Sep. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” Sep. 2018, 445 pages. [cited by applicant]
CATT, “Summary of Offline Discussion on RMSI,” 3GPP TSG RAN WG1 Meeting #92bis, R1-1805600, Sanya, China, Apr. 16-20, 2018, 17 pages. [cited by applicant]
CATT, “Summary of Remaining RMSI Issues,” 3GPP TSG RAN WG1 Meeting #94, R1-1809794, Gothenburg, Sweden, Aug. 20-24, 2018, 6 pages. [cited by applicant]
MediaTek Inc., “Summary of Bandwidth Part Remaining Issues,” 3GPP TSG RAN WG1 Meeting #94, R1-1809929, Gothenburg, Sweden, Aug. 20-24, 2018, 19 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201811642765.X on Apr. 2, 2021, 14 pages (with English translation). [cited by applicant]
PCT International Search Report and Written Opinion issued in International Application No. PCT/CN2019/128916 on Mar. 17, 2020, 17 pages (with English translation). [cited by applicant]
Samsung, “CR to 38.213 capturing the RAN1#94bis meeting agreements,” 3GPP TSG RAN WG1 Meeting #94bis, R1-1812092, Chengdu, China, Oct. 8-12, 2018, 102 pages. [cited by applicant]
Extended European Search Report issued in European Application No. 19903925.6 on Feb. 16, 2022, 11 pages. [cited by applicant]
MediaTek Inc., “Summary of Bandwidth Part Remaining Issues,” 3GPP TSG RAN WG1 Meeting #94bis, R1-1811850, Chengdu, China, Oct. 8-12, 2018, 25 pages. [cited by applicant]
NTT Docomo, Inc., “Discussion on Coreseto,” 3GPP TSG RAN WG1 Meeting #95, R1-1813934, Spokane, USA, Nov. 12-16, 2018, 80 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201811642765.X on Apr. 6, 2022, 6 pages (with English translation). [cited by applicant]
Huawei et al., “Remaining Issues on Bandwidth Part and CA,” 3GPP TSG RAN WG1 Meeting #94, R1-1808104, Gothenburg, Sweden, Aug. 20-24, 2018, 23 pages. [cited by applicant]
MediaTek Inc., “Summary of Bandwidth Part Remaining Issues,” 3GPP TSG RAN WG1 Meeting #94, R1-1809849, Gothenburg, Sweden, Aug. 20-24, 2018, 23 pages. [cited by applicant]
Office Action issued in Korean Application No. 2021-7023695 on Aug. 17, 2022, 11 pages (with English translation). [cited by applicant]
Vivo, “Remaining Issues on Bandwidth Parts,” 3GPP TSG RAN WG1 Meeting #94bis, R1-1810372, Chengdu, China, Oct. 8-12, 2018, 4 pages. [cited by applicant]